1 Reply Latest reply on May 4, 2009 4:49 PM by Carlo de Wolf

    ThreadLocalPool - Seam and Stateful Session Beans potential

    Milos Zikic Newbie

      Hello all,

      I have a big application built using Seam 2.1.1GA and deployed on JBoss 4.2.3.GA. EJB3 is used and they are injected by using seams @In annotation.

      Under heavy load memory starts to grow and never comes back. The only resolution is to restart the server.

      By analyzing heap I've found that there are a lot of SFSB instances in the ThreadLocalPool that should be destroyed but they stay somehow referenced.

      I've put timeout value on CacheConfig so the beans should definitely be destroyed but that doesn't happen.
      In the application there are some SFSB EJBs that reference other SFSB but generaly they don't hold any state. SFSB are mostly used because of extended persistentcontext.

      Are there any recommendation on this topic?

      I've googled around and found some comments on using StrictMaxPool, but I still didn't try it.

      I want to know has anyone else experienced this kind of problem.