| Key: |
POOL-125
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Phil Steitz
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Blocker
|
|
This issue blocks:
|
|
DBCP-44
[dbcp] Evictor thread in GenericObjectPool has potential for deadlock
|
|
|
|
|
|
|
|
| Resolution Date: |
12/May/09 06:08 PM
|
|
In pool 1.2, 1.4, borrowObject, returnObject, invalidateObject are not fully synchronized. This creates the potential for race conditions vis a vis the Evictor and/or client object lock contention. Factory methods on pooled objects should not be allowed to be invoked concurrently by client threads and the Evictor.
|
|
Description
|
In pool 1.2, 1.4, borrowObject, returnObject, invalidateObject are not fully synchronized. This creates the potential for race conditions vis a vis the Evictor and/or client object lock contention. Factory methods on pooled objects should not be allowed to be invoked concurrently by client threads and the Evictor. |
Show » |
| No work has yet been logged on this issue.
|
|
