1 Reply Latest reply on Mar 20, 2012 5:57 PM by Cosmin Zamfir

    LocalThreadPool.release() always remove the BeanContext

    Cosmin Zamfir Newbie



      Using a LocalThreadPool for stateless session beans in JBoss 5.1.GA seems not to work as expected.

      Ejb instances are not pooled in the current thread context; instead an (expensive) instantiation is triggered for each request.

      The reason seems to be in the LocalThreadPool.release(BeanContext ctx) which practically always : (if currentBeanContext.get() is not null - this should be always true in the release() method).


      Is this a known bug in the LocalThreadPool ?