-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
4.2.0.GA_CP01 , 4.3.0.GA
-
None
-
Medium
ThreadlocalPool does not remove active BeanContext instances from InfinitePool which
results on a memory leak.
I'm having the customer test a possible workaround which involves using StrictMaxPool,
which does not has this issue, rather than ThreadlocalPool. I'll update asap.
- duplicates
-
JBPAPP-547 ThreadlocalPool does not remove active BeanContext instances from InfinitePool
- Resolved
- incorporates
-
EJBTHREE-1175 ThreadlocalPool does not remove active BeanContext instances from InfinitePool
- Resolved