|
If you were logged in you would be able to see more operations.
|
|
Sesame
Created: 31/Mar/10 09:21 AM
Updated: 31/Mar/10 11:12 AM
|
|
| Component/s: |
Memory Sail,
Native Sail
|
| Affects Version/s: |
2.3.1,
2.3.0,
2.3-pr1,
2.2.4,
2.2.3,
2.2.2,
2.2.1,
2.1.4,
2.2,
2.1.3,
2.1.2,
2.1.1,
2.1,
2.0.1,
2.0
|
| Fix Version/s: |
2.3.2
|
|
There's a possible deadlock between a thread calling SailBase.shutDown() and a thread calling SailBase.connectionClosed(SailConnection) via SailConnectionBase.close(). The deadlock occurs when the former thread tries to call SailConnectionBase.close() to forcefully close a connection, while the latter thread is already closing that connection. The former thread holds the synchronization lock on SailBase.activeConnections and is trying to acquire a write lock on SailConnectionBase.connectionLock, while the latter thread is waiting for the synchronization lock on SailBase.activeConnections and is holding the write lock on SailConnectionBase.connectionLock.
|
|
|
There are no comments yet on this issue.
|
| |
|
|
Bug
Resolved
Critical
Deadlock while shutting down repository