2 Replies Latest reply on Oct 15, 2011 7:19 AM by wdfink

    jboss 6 boot time

    worst-case

      Hi all,

       

      I searched in the forum and couldnt find a related topic. Forgive me if I missed one. I newly switched to jboss AS and started with jboss 6 final. I created a try-out application and exploded to the server. When I boot it by using run.bat, it takes really long time (2 min+) to boot it. The application works fine, the connection to the mysql db is fine. My problem is about the booting time and when I hot-deploy, it takes 1 or 2 mins to get the application running.  JVM options are below, I hope you can find an answer.

       

      JAVA_OPTS="-Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"

         -XX:+UseConcMarkSweepGC -XX:+CMSPermGenSweepingEnabled

         -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=512m

         -XVerify:none

         -Xrs

        • 1. Re: jboss 6 boot time
          starver

          I tried this on JBoss-6.0.0.Final and found

           

             Unrecognized option: -XVerify:none

              Please use CMSClassUnloadingEnabled in place of CMSPermGenSweepingEnabled in the future

           

          I cleaned up the double quotes, double MaxPermSize and used

           

          '-Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -Xrs'

           

          From a clean start I got the following on my mac:

           

          2011-10-14 21:02:44,298 [INFO ] [Thread-3] JBossAS [6.0.0.Final "Neo"] Started in 15s:962ms (org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask:423)

          • 2. Re: jboss 6 boot time
            wdfink

            Do you see a time gap in the logfile, it may give a hint.

            Also what if you start the fresh jbossAS6?

            Also it may happen that the CMSPermGenSweepingEnabled and CMSClassUnloadingEnabled option will be the cause, so what if you switch it off?