-
Bug
-
Resolution: Done
-
Critical
-
1.0.6.Final, 1.1.0.Alpha4
-
None
-
Workaround Exists
-
In order to cleanup pools with a sparse Subject/CRI coverage we shutdown the pool if it is empty.
However, there is no reason to do so if it is the only pool available. Furthermore we should always try and allocate a connection in order to kick the allocation mechanism into effect.
- is related to
-
JBAS-5929 Sub Pooling in JBossManagedConnectionPool MemoryLeak for sparse CRI coverage
- Closed