1 2 Previous Next 16 Replies Latest reply on Apr 15, 2011 11:31 AM by Peter Johnson

    Jboss crash out of memory

    Rajasundaram Gopalan Novice

      We are having out of memory problem and not able to figure out where it is happening either the application or environment. Please help us....

       

       

      JAVA_OPTS: -Dprogram.name=run.sh -server  -Xms1536m -Xmx1536m -XX:PermSize=512M -XX:MaxPermSize=512M -XX:+DisableExplicitGC -XX:MaxNewSize=64m -XX:NewSize=64m -XX:SurvivorRatio=256 -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:MaxTenuringThreshold=0 -XX:CMSInitiatingOccupancyFraction=60 -verbose:gc -XX:+PrintGCDetails -XX:+PrintTenuringDistribution -XX:+PrintGCTimeStamps -Xloggc:/opt/ion/logs/gc.log -Dcom.sun.management.jmxremote.port=8082 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/opt/ion/logs -Djava.net.preferIPv4Stack=true

       

      Java version: 1.6.0_13

       

      JBoss [Trinity] 4.2.3.GA

       

       

       

      20:15:22,583 ERROR [[cgi]] Servlet.service() for servlet cgi threw exception

      java.lang.OutOfMemoryError: unable to create new native thread

      at java.lang.Thread.start0(Native Method)

      at java.lang.Thread.start(Thread.java:597)

      at java.lang.UNIXProcess$1.run(UNIXProcess.java:141)

      at java.security.AccessController.doPrivileged(Native Method)

      at java.lang.UNIXProcess.<init>(UNIXProcess.java:103)

      at java.lang.ProcessImpl.start(ProcessImpl.java:65)

      at java.lang.ProcessBuilder.start(ProcessBuilder.java:452)

      at java.lang.Runtime.exec(Runtime.java:593)

      at java.lang.Runtime.exec(Runtime.java:431)

      at org.apache.catalina.servlets.CGIServlet$CGIRunner.run(CGIServlet.java:1671)

      at org.apache.catalina.servlets.CGIServlet.doGet(CGIServlet.java:587)

      at org.apache.catalina.servlets.CGIServlet.doPost(CGIServlet.java:549)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)

      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

      at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)

      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)

      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

      at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)

      at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:562)

      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)

      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)

      at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)

      at java.lang.Thread.run(Thread.java:619)

      20:15:22,919 ERROR [[cgi]] Servlet.service() for servlet cgi threw exception

      java.lang.OutOfMemoryError: unable to create new native thread

      at java.lang.Thread.start0(Native Method)

      at java.lang.Thread.start(Thread.java:597)

      at java.lang.UNIXProcess$1.run(UNIXProcess.java:141)

      at java.security.AccessController.doPrivileged(Native Method)

      at java.lang.UNIXProcess.<init>(UNIXProcess.java:103)

      at java.lang.ProcessImpl.start(ProcessImpl.java:65)

      at java.lang.ProcessBuilder.start(ProcessBuilder.java:452)

      at java.lang.Runtime.exec(Runtime.java:593)

      at java.lang.Runtime.exec(Runtime.java:431)

      at org.apache.catalina.servlets.CGIServlet$CGIRunner.run(CGIServlet.java:1671)

      at org.apache.catalina.servlets.CGIServlet.doGet(CGIServlet.java:587)

      at org.apache.catalina.servlets.CGIServlet.doPost(CGIServlet.java:549)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

      at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

      at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

      at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

      at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

      at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)

      at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

      at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)

      at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)

      at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

      at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

      at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)

      at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:562)

      at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

      at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)

      at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

      at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)

      at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)

      at java.lang.Thread.run(Thread.java:619)

      20:15:23,110 ERROR [STDERR] java.lang.OutOfMemoryError: unable to create new native thread

      20:15:23,110 ERROR [STDERR]  at java.lang.Thread.start0(Native Method)

      20:15:23,110 ERROR [STDERR]  at java.lang.Thread.start(Thread.java:597)

      20:15:23,110 ERROR [STDERR]  at HTTPClient.HTTPConnection.getSocket(HTTPConnection.java:3128)

      20:15:23,110 ERROR [STDERR]  at HTTPClient.HTTPConnection.sendRequest(HTTPConnection.java:2879)

      20:15:23,110 ERROR [STDERR]  at HTTPClient.HTTPConnection.handleRequest(HTTPConnection.java:2715)

      20:15:23,110 ERROR [STDERR]  at HTTPClient.HTTPConnection.setupRequest(HTTPConnection.java:2507)

      20:15:23,110 ERROR [STDERR]  at HTTPClient.HTTPConnection.Post(HTTPConnection.java:1050)

      20:15:23,110 ERROR [STDERR]  at HTTPClient.HTTPConnection.Post(HTTPConnection.java:920)

      20:15:23,110 ERROR [STDERR]  at sun.reflect.GeneratedMethodAccessor1772.invoke(Unknown Source)

      20:15:23,110 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

      20:15:23,110 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:597)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:142)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:201)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3084)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2250)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:149)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:337)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2755)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:160)

      20:15:23,111 ERROR [STDERR]  at org.mozilla.javascript.Context.evaluateString(Context.java:1132)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.javascript.JavaScriptContext$ScriptingEngine.execute(JavaScriptContext.java:126)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.common.actions.ScriptedAction.execute(ScriptedAction.java:73)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.runtime.Action.execute(Action.java:133)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.runtime.Sequence.next(Sequence.java:108)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.runtime.Execution$1.run(Execution.java:173)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.http.DeploymentExecution.visitRunnable(DeploymentExecution.java:479)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.runtime.Execution$1.accept(Execution.java:187)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.http.DeploymentExecution.doNext(DeploymentExecution.java:198)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.http.DeploymentSession.next(DeploymentSession.java:231)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.http.Deployment.next(Deployment.java:178)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.http.HttpConnector.invokeProcessEngine(HttpConnector.java:401)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.http.HttpConnector.process(HttpConnector.java:298)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.http.HttpConnectorServlet.process(HttpConnectorServlet.java:121)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.vtp.framework.engine.http.HttpConnectorServlet.doPost(HttpConnectorServlet.java:164)

      20:15:23,111 ERROR [STDERR]  at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)

      20:15:23,111 ERROR [STDERR]  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75)

      20:15:23,111 ERROR [STDERR]  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

      20:15:23,111 ERROR [STDERR]  at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:115)

      20:15:23,111 ERROR [STDERR]  at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

      20:15:23,112 ERROR [STDERR]  at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

      20:15:23,112 ERROR [STDERR]  at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)

      20:15:23,112 ERROR [STDERR]  at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)

      20:15:23,112 ERROR [STDERR]  at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:562)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)

      20:15:23,112 ERROR [STDERR]  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)

      20:15:23,112 ERROR [STDERR]  at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)

      20:15:23,112 ERROR [STDERR]  at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)

      20:15:23,112 ERROR [STDERR]  at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)

      20:15:23,112 ERROR [STDERR]  at java.lang.Thread.run(Thread.java:619)

      #

      # An unexpected error has been detected by Java Runtime Environment:

      #

      # java.lang.OutOfMemoryError: requested 6007184 bytes for GrET in /BUILD_AREA/jdk6_13/hotspot/src/share/vm/utilities/growableArray.cpp. Out of swap space?

      #

      #  Internal Error (allocation.inline.hpp:42), pid=24375, tid=803990416

      #  Error: GrET in /BUILD_AREA/jdk6_13/hotspot/src/share/vm/utilities/growableArray.cpp

      #

      # Java VM: Java HotSpot(TM) Server VM (11.3-b02 mixed mode linux-x86)

      # An error report file with more information is saved as:

      # /usr/local/jboss-4.2.3.GA/server/default/deploy/hs_err_pid24375.log

      #

      # If you would like to submit a bug report, please visit:

      #   http://java.sun.com/webapps/bugreport/crash.jsp

      #

        • 1. Jboss crash out of memory
          Peter Johnson Master

          This error message:

           

          java.lang.OutOfMemoryError: unable to create new native thread

           

          means that you are exhausting the addressable address space of your process. Thus your are not running out of heap memory. Actually, setting the heap to 1.5GB like you have done is part of the problem - you are using too much of the address space for the heap and not allowing enough for other things.

           

          I assume you are running a 32-bit JVM, in which case you have only a 4GB address space. Depending on your OS, 1-2GB of that space is used by the OS. Between that heap and permgen you are using up another 2GB. Then all of the code for the JVM and the libraries it needs have to go in there also. This leaves precious little space for thread, each of which consume anywhere from 512KB to 1MB (again depending on the OS).

           

          You can try decreasing the thread stack size via the -XX:ThreadStackSize=xxx JVM option. You might also try decreasing the heap size.

          • 2. Re: Jboss crash out of memory
            Rajasundaram Gopalan Novice

            Thanks peter we will make the changes and let you know the status back.

             

            I did the code review and found in most of our code we call ejb beans by establishing initialcontext and we did not close the initial context in the finally block will it be an issue for

            potential resource leak?

             

            please let me know should I need to modify all our code to close the initial context?

            • 3. Jboss crash out of memory
              Wolf-Dieter Fink Master

              That is not correct,

              but I found it in our code sometimes as well and it should be not such a big problem.

              I suppose another problem.

              • 4. Jboss crash out of memory
                Rajasundaram Gopalan Novice

                thanks.

                 

                Do you have any suggestions or tools can be used to find where the memory leak is happening.

                 

                I read following JIRA about the memory leak

                 

                http://jira.opensymphony.com/browse/QUARTZ-260

                 

                We have separate jboss server for Applications and Services.

                 

                ejbs are deployed in separate jboss server (we call as service box) and applications are deployed in separate jboss server( we call as application box)

                 

                applications calls ejbs remotely. Will it make any difference because in the article says InitialContexts are like database connections.

                 

                Please clarify me.

                 

                Thanks for your help.

                • 5. Jboss crash out of memory
                  Wolf-Dieter Fink Master

                  From your post I suggest that your service box is running but the application box will have the memory problem.

                  As I wrote before, it is a good practice to close the InitialContext if it is not longer used.

                   

                  We use jProfiler and trigger a heap dump for two or more times during we run a load test, ok troughput is not high but it dosn't matter in this case.

                  With jProfiler you can analyse and compare the thread dumps to see whether there are more objects than expected and increased over the time.

                  (Also NetBeans profiler or others might have the same functionality)

                  • 6. Jboss crash out of memory
                    Rajasundaram Gopalan Novice

                    Thanks..

                     

                    Yes we have memory issue in application box (client). Let us try to use jprofiler.

                    • 7. Jboss crash out of memory
                      Rico Neubauer Novice

                      The message does not neccessarily mean that you are having a memory problem (in the manner of heap or native memory), but you can also reach the thread-limit of you OS.

                      e.g. in HP-UX, this is defined in this way:

                      max_thread_proc - Specifes the maximum number of threads a single process is allowed to have.

                      • 8. Jboss crash out of memory
                        Peter Johnson Master

                        As I pointed out, and Rico reiterated, the problem you are having is not with a memory leak, it is not the heap that is filling up. It is an OS resource issue. Examining the code for memory leaks or analyzing heap memory usage will not help you solve the problem.

                         

                        A thread dump can tell you how many threads you have.

                         

                        By the way, what OS are you using?

                        • 9. Re: Jboss crash out of memory
                          Rajasundaram Gopalan Novice

                          We are using red hat linux operating system:

                           

                          http://jbapp:8080/status?full=true

                           

                          JVM

                          Free memory: 640.56 MB Total memory: 1535.81 MB Max memory: 1535.81 MB

                          http-0.0.0.0-8080

                          Max threads: 500 Current thread count: 43 Current thread busy: 10
                          Max processing time: 62406 ms Processing time: 72648.8 s Request count: 1059658 Error count: 414 Bytes received: 3656.18 MB Bytes sent: 1729.95 MB

                          StageTimeB SentB RecvClientVHostRequest
                          K361 ms??10.75.250.32??


                          At present the thread count is 43.

                           

                          Some of our code was not closed AudioInputStream and OutputStream do you think it may be an issue?

                           

                          Please let us know how to do Thread Dump do I need any tool or does it comes with jboss itself.

                           

                          Thanks

                          • 10. Re: Jboss crash out of memory
                            Rajasundaram Gopalan Novice

                            Thread Dump from jmx-console

                             

                            List of MBean attributes:

                            NameTypeAccessValueDescription
                            ActiveThreadCountjava.lang.IntegerR308 MBean Attribute.
                            AvailableProcessorsjava.lang.IntegerR4 MBean Attribute.
                            OSArchjava.lang.StringRi386 MBean Attribute.
                            MaxMemoryjava.lang.LongR1610416128 MBean Attribute.
                            HostAddressjava.lang.StringR10.75.254.140 MBean Attribute.
                            JavaVersionjava.lang.StringR1.6.0_13 MBean Attribute.
                            OSVersionjava.lang.StringR2.6.18-194.3.1.el5 MBean Attribute.
                            JavaVendorjava.lang.StringRSun Microsystems Inc. MBean Attribute.
                            TotalMemoryjava.lang.LongR1610416128 MBean Attribute.
                            ActiveThreadGroupCountjava.lang.IntegerR10 MBean Attribute.
                            OSNamejava.lang.StringRLinux MBean Attribute.
                            FreeMemoryjava.lang.LongR703417728 MBean Attribute.
                            HostNamejava.lang.StringRjbapp1.com MBean Attribute.
                            JavaVMVersionjava.lang.StringR11.3-b02 MBean Attribute.
                            JavaVMVendorjava.lang.StringRSun Microsystems Inc. MBean Attribute.
                            JavaVMNamejava.lang.StringRJava HotSpot(TM) Server VM MBean Attribute.

                            Attached file contains thread dump

                            • 11. Re: Jboss crash out of memory
                              Peter Johnson Master

                              You have 305 threads, not 43. The 43 was the number of HTTP threads that were active; there are many other kinds of threads running within the JVM. I don't think that RHEL by default limits the number of running threads. So at this point I think that the original advice I gave is the best..

                              • 12. Re: Jboss crash out of memory
                                Rajasundaram Gopalan Novice

                                43 threads are serving web applications and rest of them are Open Method callflow application.

                                 

                                Some of our code was not closed AudioInputStream do you think it may be an issue as well? this was called lot of times.

                                 

                                And I read following bug report:

                                 

                                http://bugs.sun.com/view_bug.do?bug_id=6423256

                                 

                                Do you think this may be problem we are using jdk6 update 13

                                 

                                 

                                 

                                # If you would like to submit a bug report, please visit:
                                #   http://java.sun.com/webapps/bugreport/crash.jsp
                                #

                                ---------------  T H R E A D  ---------------

                                Current thread (0x09b92c00):  VMThread [stack: 0x2fe3e000,0x2febf000] [id=24382]

                                Stack: [0x2fe3e000,0x2febf000],  sp=0x2febdb50,  free space=510k
                                Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
                                V  [libjvm.so+0x60671b]
                                V  [libjvm.so+0x2d3a11]
                                V  [libjvm.so+0x34874c]
                                V  [libjvm.so+0x32fd3e]
                                V  [libjvm.so+0x32f621]
                                V  [libjvm.so+0x2bab40]
                                V  [libjvm.so+0x2ba52e]
                                V  [libjvm.so+0x2ba245]
                                V  [libjvm.so+0x32cddb]
                                V  [libjvm.so+0x32dd18]
                                V  [libjvm.so+0x32d90c]
                                V  [libjvm.so+0x34bc25]
                                V  [libjvm.so+0x614907]
                                V  [libjvm.so+0x613f1c]
                                V  [libjvm.so+0x6140f1]
                                V  [libjvm.so+0x613ccf]
                                V  [libjvm.so+0x506929]
                                C  [libpthread.so.0+0x5832]

                                VM_Operation (0x08b07ea0): HeapDumper, mode: safepoint, requested by thread 0x24a75000

                                • 13. Re: Jboss crash out of memory
                                  Peter Johnson Master

                                  I image that an AudioInpuitStream will use up OS resources, each of which take up processor memeory space, so yes those unclosed streams could cause thep rocess to run out of memory.

                                  • 14. Re: Jboss crash out of memory
                                    Rico Neubauer Novice

                                    You can also heck for the No. of used file handles (e.g. using lsof) and compare them to your user's limit (ulimit -n and ulimit -Hn), despite this normally is seen with a more informative log message.

                                    1 2 Previous Next