-
Bug
-
Resolution: Done
-
Major
-
3.0.16.Final, 1.5.23.Final
-
None
-
None
This issue is a follow-up. As stated in the comment in JBJCA-1511 per connection synchronization in getConnection and returnConnection helped to deal with leaks associated with disassociation and external scenarios. The aim of this task is to replicate such synchronization for idle connection removal functionality which still leads to leaks in my stress tests.
- is related to
-
JBJCA-1526 Idle runner: add configuration which will allow for stress testing the pool
-
- Open
-
-
JBEAP-31928 [GSS](8.0.11 patch) Upgrade ironjacamar from 3.0.14.Final-redhat-00001 to 3.0.18.Final-redhat-00001
-
- Resolved
-
-
JBEAP-31881 [GSS](8.1.z) Upgrade ironjacamar from 3.0.14.Final-redhat-00001 to 3.0.18.Final-redhat-00001
-
- Resolved
-
-
WFLY-21385 Upgrade ironjacamar to 3.0.18.Final
-
- Resolved
-
- relates to
-
JBJCA-1511 SemaphoreConcurrentLinkedDequeManagedConnectionPool: per connection synchronization in getConnection and returnConnection
-
- Open
-