Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
- Timestamp:
-
05/13/08 15:10:07 (16 years ago)
- Author:
-
jmoore
- Comment:
-
Finally reproduced on my box. All it takes to reproduce the server freeze is to start 50 threads at the same time all of which call IAdmin.getEventContext(). c3p0 (the JDBC connection pool) then locks. Looking into solutions.
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Status
changed from
new
to
assigned
- Property Cc callan added
-
Property
Component
changed from
General
to
Services
-
Property
Summary
changed from
server Freeze
to
Server deadlock on empty connection pool
-
Property
Version
changed from
3.0-M3
to
- Property Owner changed from jmoore, callan to jmoore
-
|
v3
|
v15
|
|
| 1 | | The problem happened twice |
| 2 | | Suddenly, the server freezes for no particular reasons |
| 3 | | and seems to enter in an infinite loop. |
| | 1 | When too many methods are executing simultaneously, the connection pool can lock up, causing the server to freeze and all methods to fail. `kill -9` is required to stop the server. |
| | 2 | |
| | 3 | One symptom of the freeze is that the `FullTextThread` blocks while indexing, causing other `FullTextThreads` to print: |
| 4 | 4 | |
| 5 | 5 | {{{ |
| … |
… |
|
| 8 | 8 | |
| 9 | 9 | |
| 10 | | |
| 11 | | That's the message returned by the server. |
| 12 | | The standard Stop procedure no longer works, a force quit is required. |
| 13 | | |
1.3.13-PRO © 2008-2011
Agilo Software all
rights reserved
(this page was served in: 0.15600 sec.)
