9 Replies Latest reply on Jan 19, 2011 9:25 AM by peterj

    Getting OutOfMemoryError:Java heap space error

    mkothari

      java.lang.OutOfMemoryError:Java heap space

                 at java.util.HashMap.addEntry(HashMap.java:797)

                 at java.util.HashMap.put(HashMap.java:431)

                 at com.documentum.fc.client.impl.typeddata.AggregateLiteType.addAttrInternal(AggregateLiteType.java:430)

                 atcom.documentum.fc.client.impl.typeddata.AggregateLiteType.addAttrInternal(AggregateLiteType.java:423)

                 at com.documentum.fc.client.impl.typeddata.AggregateLiteType.buildMapping(AggregateLiteType.java:344)

                 atcom.documentum.fc.client.impl.typeddata.AggregateLiteType.<init>(AggregateLiteType.java:35)

                 at com.documentum.fc.client.impl.typeddata.AggregateLiteType.getUnextendedType(AggregateLiteType.java:103)

                 atcom.documentum.fc.client.impl.connection.LiteTypeManager.extractAspectTypeNames(LiteTypeManager.java:328)

                 at com.documentum.fc.client.impl.connection.LiteTypeManager.refreshTypeIfNeeded(LiteTypeManager.java:303)

                 atcom.documentum.fc.client.impl.objectprotocol.ObjectProtocolV1.deserializeObject(ObjectProtocolV1.java:91)

                 atcom.documentum.fc.client.impl.objectprotocol.ObjectProtocolV1.deserializeObjectWithPossiblyExtendedType(ObjectProtocolV1.java:203)

                 atcom.documentum.fc.client.impl.objectprotocol.ObjectProtocolV1.deserializeObjectWithPreamble(ObjectProtocolV1.java:309)

                 at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.applyForObject(NetwiseDocbaseRpcClient.java:663)

                 atcom.documentum.fc.client.impl.connection.docbase.DocbaseConnection$8.evaluate(DocbaseConnection.java:1246)

                 at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.evaluateRpc(DocbaseConnection.java:1014)

                 atcom.documentum.fc.client.impl.connection.docbase.DocbaseConnection.applyForObject(DocbaseConnection.java:1238)

                 at com.documentum.fc.client.impl.docbase.DocbaseApi.parameterizedFetch(DocbaseApi.java:106)

                 atcom.documentum.fc.client.impl.objectmanager.PersistentDataManager.fetchFromServer(PersistentDataManager.java:194)

                 atcom.documentum.fc.client.impl.objectmanager.PersistentDataManager.getData(PersistentDataManager.java:92)

                 atcom.documentum.fc.client.impl.objectmanager.PersistentObjectManager.getObjectFromServer(PersistentObjectManager.java:355)

                 atcom.documentum.fc.client.impl.objectmanager.PersistentObjectManager.getObject(PersistentObjectManager.java:311)

                 at com.documentum.fc.client.impl.session.Session.getObject(Session.java:834)

                 atcom.documentum.fc.client.impl.session.SessionHandle.getObject(SessionHandle.java:580)

                 at com.bureauveritas.documentum.common.dql.ExecDQL.queryForList(Unknown Source)

                 at com.bureauveritas.documentum.common.dql.ExecDQL.queryForList(Unknown Source)

                 atcom.bureauveritas.documentum.ismt.alertnotification.BvAlertNotificationJob.getExceededDueDate(UnknownSource)

                 atcom.bureauveritas.documentum.ismt.alertnotification.BvAlertNotificationJob.performJob(UnknownSource)

                 at com.bureauveritas.documentum.common.job.ABvCommonJob.performMethod(UnknownSource)

                 at com.bureauveritas.documentum.common.method.ABvCommonMethod.perform(UnknownSource)

                 at com.bureauveritas.documentum.common.method.ABvCommonMethod.execute(UnknownSource)

                 at com.documentum.mthdservlet.DfMethodRunner.runIt(Unknown Source)

                 at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)

      06:12:38,598ERROR [http-0.0.0.0-9080-1] com.documentum.mthdservlet.DoMethod - Exceptioninvoking bv_mod_icc_dctm_alertnotification.

      ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error

                 at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:319)

                 at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:288)

                 atorg.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.java:98)

                 at com.documentum.mthdservlet.MethodOutputStream.flush(Unknown Source)

                 at com.documentum.mthdservlet.MethodOutputStream.flush(Unknown Source)

                 at com.documentum.mthdservlet.MethodOutputStream.methodClose(Unknown Source)

                 at com.documentum.mthdservlet.AMethodRunner.runAndReturnStatus(Unknown Source)

                 at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)

                 at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)

                 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)

                 atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

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

                 atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

                 atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

                 atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)

                 atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

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

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

                 atorg.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)

                 atorg.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)

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

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

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

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

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

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

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

      Causedby: java.net.SocketException: Software caused connection abort: socket writeerror

                 at java.net.SocketOutputStream.socketWrite0(Native Method)

                 at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)

                 at java.net.SocketOutputStream.write(SocketOutputStream.java:136)

                 atorg.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737)

                 at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434)

                 atorg.apache.coyote.http11.InternalOutputBuffer.flush(InternalOutputBuffer.java:299)

                 at org.apache.coyote.http11.Http11Processor.action(Http11Processor.java:963)

                 at org.apache.coyote.Response.action(Response.java:183)

                 at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:314)

                 ... 28 more

      06:12:38,598ERROR [http-0.0.0.0-9080-1]org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/DmMethods].[DoMethod]- Servlet.service() for servlet DoMethod threw exception

      javax.servlet.ServletException:ClientAbortException:  java.net.SocketException: Software causedconnection abort: socket write error

                 at com.documentum.mthdservlet.DoMethod.invokeMethod(Unknown Source)

                 at com.documentum.mthdservlet.DoMethod.doPost(Unknown Source)

                 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)

                 atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

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

                 atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

                 atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

                 atorg.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)

                 atorg.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)

                 atorg.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)

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

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

                 atorg.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)

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

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

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

        • 1. Getting OutOfMemoryError:Java heap space error
          peterj

          Increase the heap size.

           

          (Which version of JBoss AS, which OS, which JVM, what JVM settings?)

          • 2. Getting OutOfMemoryError:Java heap space error
            mkothari

            I am new to Jboss, Followng is version of Jboss

             

            JBoss [EAP] 4.2.0.GA_CP01 , on Windows 2003 SP2, Please let me know where exactly I have to modify the parameter to avoid this error.

             

            Thanks,

            • 3. Getting OutOfMemoryError:Java heap space error
              wdfink

              If you start with bin/run.bat you try to modify the line:

              set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m

              and increase the -Xmx value.

              Also it might help to increase -Xms if you need the memory constantly (it will increase the initial heap size and free the JVM to recalculate the heap)

              • 4. Getting OutOfMemoryError:Java heap space error
                mkothari

                thanks for your response, I am running as windows service, which refers to exe, which batch file to make this change ?

                • 5. Getting OutOfMemoryError:Java heap space error
                  peterj

                  What tool or package are you using to run JBoss AS as a Windows service? If you are using JBoss Native, then follow Wolf-Dieter's advice. If you are using Tanuki Java Service then you will have to edit the registry. If neither of these two, provide a URL for the one you are using.

                  • 6. Getting OutOfMemoryError:Java heap space error
                    mkothari

                    Actually I am using JBOSS as method server as part of one of Content meanagement tool "Documentum". So If I check Properties of Jboss method server service , I find only .exe location , being called, how to track exact batch file to make ncessary change ?

                    • 7. Re: Getting OutOfMemoryError:Java heap space error
                      peterj

                      Documentum from EMC? (http://www.emc.com/domains/documentum/index.htm) I assume you paid for support for that, so why aren't you asking EMC about this? It is a defect in their product, after all.

                       

                      Otherwise, since I am not about to download Documentum (even if I could), you will have to tell me a whole lot more about how JBoss AS is fired up by Documententum. Exactly what mechanisms does it use? And if it doesn't use the JBoss AS batch files to run JBoss AS, exactly how does it run it? Is there any documentation that comes with Documentum that describes how to change the JBoss AS configuration? Saying "I find only .exe location , being called" is not sufficient - I don't have any idea what that even means.

                      • 8. Re: Getting OutOfMemoryError:Java heap space error
                        mkothari

                        We have basic support, to get response from them would take time, by that time I would like to implement some workaround, if that do not work, definately will raise support request with EMC.

                         

                        As far as I know the Windows service is started using dctmservice.exe and the configuration given in %Documentum%\jboss4.2.0\server\serviceConfig\MethodServer\conf\wrapper.conf. The wrapper.conf refers to DmMethodServer.xml (in the same folder) which specifies using startMthodServer.cmd to start the Method Server.

                         

                        So I believe "startMthodServer.cmd", right place to set the Java OPTS ?

                        • 9. Re: Getting OutOfMemoryError:Java heap space error
                          peterj
                          So I believe "startMthodServer.cmd", right place to set the Java OPTS ?

                          I have no idea what is in that file - it is not a standard JBoss AS file. And you didn't post it.You could always compare it to run.bat and run.conf.bat in the JBoss AS binary download.