4 Replies Latest reply on Dec 2, 2010 4:01 AM by jaikiran pai

    OOM error when accessing my application after jboss 5.1.0 is deployed

    mike just Master

      Any idea about this OOM error? I think my jvm parameter is already high enough: -Xms512m -Xmx1024m -XX:MaxPermSize=512m.

       

      16:09:12,890 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
      16:09:12,937 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      16:09:13,015 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 5m:32s:703ms
      16:12:10,156 WARN  [ClassLoaderManager] Unexpected error during load of:org.eclipse.jdt.internal.compiler.flow.ConditionalFlowInfo
      16:12:21,812 ERROR [[jsp]] Servlet.service() for servlet jsp threw exception
      16:12:31,171 WARN  [ClassLoaderManager] Unexpected error during load of:org.apache.log4j.spi.ThrowableInformation
      java.lang.OutOfMemoryError: PermGen space
      16:12:34,093 ERROR [[gs]] Servlet.service() for servlet gs threw exception
      java.lang.OutOfMemoryError: PermGen space
      16:12:36,421 WARN  [ClassLoaderManager] Unexpected error during load of:org.jboss.web.tomcat.security.SecurityAssociationActions$ClearAction
      java.lang.OutOfMemoryError: PermGen space
      16:12:41,046 WARN  [ClassLoaderManager] Unexpected error during load of:org.jboss.web.tomcat.security.SecurityAssociationActions$1
      java.lang.OutOfMemoryError: PermGen space
      16:12:43,328 ERROR [CoyoteAdapter] An exception or error occurred in the container during the request processing
      16:12:48,046 ERROR [Http11Processor] Error processing request
      java.lang.OutOfMemoryError: PermGen space
      16:12:56,078 WARN  [ClassLoaderManager] Unexpected error during load of:org.apache.coyote.Constants
      java.lang.OutOfMemoryError: PermGen space
      16:12:56,078 ERROR [Http11Processor] Error finishing response
      16:13:03,031 ERROR [STDERR] Exception in thread "http-127.0.0.1-8080-1"
      16:13:09,015 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space
      16:13:09,031 ERROR [STDERR] Exception in thread "QuartzScheduler_QuartzScheduler-NON_CLUSTERED_MisfireHandler"
      16:13:09,046 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space

        • 1. Re: OOM error when accessing my application after jboss 5.1.0 is deployed
          jaikiran pai Master

          Which operating system? And how do you start the server? Post the initial few lines from the console log which show the JVM params being used.

          • 2. Re: OOM error when accessing my application after jboss 5.1.0 is deployed
            mike just Master

            Here you are. I'm using Windows XP.

             

            C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss>set JAVA_HOME=C:/Program Files/Java/jdk1.6.0_07

            C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss>set JAVA_OPTS= -Dorg.jboss.logging.Log4jService.catchSystemOut=false

            C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss>jboss_server\bin\run.bat;
            Calling C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss\jboss_server\bin\run.conf.bat
            ===============================================================================

              JBoss Bootstrap Environment

              JBOSS_HOME: C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss\jboss_server

              JAVA: C:/Program Files/Java/jdk1.6.0_07\bin\java

              JAVA_OPTS: -Dprogram.name=run.bat  -Dorg.jboss.logging.Log4jService.catchSystemOut=false -server

              CLASSPATH: C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss\jboss_server\bin\run.jar

            ===============================================================================

            run.bat: unused non-option argument: ;
            16:03:40,265 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
            16:03:40,296 INFO  [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)

            • 3. Re: OOM error when accessing my application after jboss 5.1.0 is deployed
              mike just Master

              16:03:49,609 INFO  [ServerInfo] Java version: 1.6.0_07,Sun Microsystems Inc.
              16:03:49,609 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
              16:03:49,609 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b23,Sun Microsystems Inc.
              16:03:49,609 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86
              16:03:49,640 INFO  [ServerInfo] VM arguments: -Dprogram.name=run.bat -Dorg.jboss.logging.Log4jService.catchSystemOut=false -Djava.endorsed.dirs=C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss\jboss_server\lib\endorsed
              16:03:49,750 INFO  [JMXKernel] Legacy JMX core initialized
              16:03:57,421 INFO  [ProfileServiceBootstrap] Loading profile: ProfileKey@127fa03[domain=default, server=default, name=default]

               

              Why is not there the parameter "-Xms512m -Xmx1024m -XX:MaxPermSize=512m" I set in run.conf.bat (set "JAVA_OPTS=-Xms512M -Xmx1024M -XX:MaxPermSize=512M") displaying in the console? I only see this one: VM arguments: -Dprogram.name=run.bat -Dorg.jboss.logging.Log4jService.catchSystemOut=false -Djava.endorsed.dirs=C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss\jboss_server\lib\endorsed.

              • 4. Re: OOM error when accessing my application after jboss 5.1.0 is deployed
                jaikiran pai Master
                C:\Welocalize\globalsight\server\GlobalSight_20101202\GlobalSight\jboss>set  JAVA_OPTS= -Dorg.jboss.logging.Log4jService.catchSystemOut=false

                Why are you doing this outside of the run.conf.bat script? Set (append) it to the JAVA_OPTS section in the run.conf.bat. This explains why you are running into all these out of memory issues.