6 Replies Latest reply on Nov 27, 2010 10:28 AM by popoctavian

    JBoss tmp filder increased size

    popoctavian

      Hi, we have a server running in JBoss. We found that the tmp folder size is over 2GB, I'm not sure if this is a normal behavior.
      For example, there was a folder under tmp: tmp/sessions/MySFB-{code} that contains more than 80 thousand files with .ser extension.

      Do you have an explanation why is increasing the tmp folder size to such values?
      Could it be caused by an inappropriate error handling in SFB classes? There is a method annotated to @Remove which normally is called when the processing is finished on stateful bean.

      Regards.

        • 1. Re: JBoss tmp filder increased size
          jaikiran

          As far as i know, the .ser files contain passivated session beans (or even HTTPSession?). So the longer your application runs, the more the size of this folder. In addition to these files, the tmp folder contains the unzipped (extracted) versions of various applications deployed on JBoss.

          • 2. Re: JBoss tmp filder increased size
            alrubinger

            Are .ser files getting deleted upon SFSB remove(); ?

            I'm not seeing the call to StatefulSessionPersistenceManager.removePassivated() that I'd expect in the RemovalTask in SimpleStatefulCache (which is used in non-clustered configurations).

            If this is the case, please open a JIRA and assign to me.

            S,
            ALR

            • 3. Re: JBoss tmp filder increased size
              alrubinger

               

              "ALRubinger" wrote:
              ... that I'd expect in the RemovalTask in SimpleStatefulCache ...


              Correction, it's not the RemovalTask which needs this, but SimpleStatefulCache.remove().

              S,
              ALR

              • 4. Re: JBoss tmp filder increased size

                Checkout the ejb3-interceptors-aop.xml, by default, it's set to 0, which indicates keep them forever.

                removalTimeoutSeconds value in the stateful session beans section


                ...

                @org.jboss.annotation.ejb.cache.simple.CacheConfig (maxSize=100, idleTimeoutSeconds=300, removalTimeoutSeconds=14400)

                • 5. Re: JBoss tmp filder increased size

                  Hi, I am running jboss-4.0.5GA and having exactly the same problem. And in that ejb3-interceptors-aop.xml file I did not find anywhere removalTimeoutSeconds value.
                  So how to get rid of those *.ser files automatically?
                  Thank you.

                  • 6. Re: JBoss tmp filder increased size
                    popoctavian

                    I managed to control the size of .ser files by calling the @Remove method when handling exception thrown sfbs.