Description
There seems to be race condition between PoolFiller and CapacityFiller which results in wrong pool statistics
I think what happens is:
- Both add connections to pool in different threads
- PoolFiller creates connection, then checks pools size and because pool has already certain size, it doesn't add connection and instead it destroys connection which increases destroyedCount
see SemaphoreConcurrentLinkedDequeManagedConnectionPool.java#L1163
Attachments
Issue Links
- blocks
-
JBEAP-9840 Unignore XADatasourceCapacityPoliciesTestCase
- Verified
- clones
-
JBJCA-1344 race condition between PoolFiller and CapacityFiller results in wrong pool statistics
- Closed