1 Reply Latest reply on Nov 19, 2015 11:35 AM by Jay SenSharma

    Whats wrong in this standalone configuration?

    rodrigo ramos Newbie

      20151119-jbossErro.png

      I have this instalation in a server, but after tests, the JBoss crash and I need Restart the JBoss

       

      My configurations:

      Arguments: -mp C:\Jboss\jboss-as-7.1.1.Final\modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=C:\Jboss\jboss-as-7.1.1.Final -b 0.0.0.0 -Dorg.apache.coyote.hpp11.Http11Protocol.SERVER=PmsjcServer

       

      JVM Arguments

      -XX:+TieredCompilation

      -Dprogram.name=standalone_original.bat

      -Xms1G

      -Xmx10G

      -XX:MaxPermSize=512M

      -XX:+UseParallelGC

      -XX:+UseParallelOldGC

      -XX:+UseAdaptiveSizePolicy

      -Dsun.rmi.dgc.client.gcInterval=600000

      -Dsun.rmi.dgc.server.gcInterval=600000

      -Djava.net.preferIPv4Stack=true

      -Dorg.jboss.resolver.warning=true

      -Djboss.modules.system.pkgs=org.jboss.byteman

      -Djboss.server.default.config=standalone.xml

      -Dorg.jboss.boot.log.file=C:\Jboss\jboss-as-7.1.1.Final\standalone\log\boot.log

      -Dlogging.configuration=file:C:\Jboss\jboss-as-7.1.1.Final\standalone/configuration/logging.properties

       

      JVM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02, mixed mode)

      Java: version 1.7.0_79, vendor Oracle Corporation

        • 1. Re: Whats wrong in this standalone configuration?
          Jay SenSharma Master

          In your screenshot we see that you are getting "OutOfMemoryError: GC overhead limit exceeded"

           

          The “GC overhead limit exceeded “ indicates that, more than 98% of the total time is spent doing garbage collection and less than 2% of the heap is recovered. The “GC overhead limit exceeded” in general represent the following cause:

          1. When the heap is too small, there is a memory leak. (Try increasing the -Xmx value while starting your process)

          2. The old generation size of the heap might be very small compared to the new generation.

          3. If increasing the Heap size (-Xmx) OR tuning the Old Generation size does not help then it might be a memory leak in the application code/container code.

           

          Better to take a heap dump and see what kind of objects are getting filled up inside the Heap, That will indicate which might be leaking or if the heap size is sufficient or not.

           

          For more details:

          OutOfMemory Causes and First Aid Steps?

          http://middlewaremagic.com/weblogic/?p=4464

           

          Regards

          Jay SenSharma