1 Reply Latest reply on May 31, 2012 8:59 AM by Periklis Douvitsas

    Jboss 5.1 really slow for one application we migrate from jboss 4

    foxxav Newbie

      Hi,

       

      We migrate 8 apps from Jboss 4.0.3SP1. Unfortunatelly we encounter a really big performance issu with one of these apps.

      These application are EJB2 and we use JDK 1.5

      When accessing a page which took 14 seconds in jboss 4 we now need under jboss 5.1 4 minutes.

       

      What can I check to determine the issue ? I start looking for issu by watching the class loading (I put -verbose:class in the lanch command) but I don't see any problems, I also look to thread with jvisualVM.

      I saw that these Methods are taking lot's of time :

      org.quartz.simpl.SimpleThreadPool.getNextRunnable()

      oracle.net.ns.Packet.receive

       

      But I'm not used to "read" all these informations so if you could give me some advices It will help me for sure.

       

      See you.

        • 1. Re: Jboss 5.1 really slow for one application we migrate from jboss 4
          Periklis Douvitsas Newbie

          Hi

          May be this link would help you

           

          https://community.jboss.org/thread/159659

          i quote

          "

          The root of the problem is found. JBoss6 defines the "Standard CMP 2.x EntityBean" configuration in standardjboss.xml by referencing the "instance per transaction" configuration, which has no transaction-independant entity bean cache:

          <container-configuration extends="Instance Per Transaction CMP 2.x EntityBean"> <container-name>Standard CMP 2.x EntityBean</container-name> </container-configuration> 

           

          This was a killer for our application, since there are huge imutable entities, which get loaded in the cache once and should not be reloaded afterwards.

          By replacing "Standard CMP 2.x EntityBean" to use a configuration like "Standard Pessimistic CMP 2.x EntityBean" this problem was gone and performance is good - about 50% more than with JBoss4. But some transaction issues remain as mentioned."