7 Replies Latest reply: Apr 7, 2010 8:20 AM by Greg @ Innisfree ZA RSS

    Java.lang.OutOfMemoryError while running config manager

    Greg @ Innisfree ZA

      Let's start off by stating that I'm not a WAS expert.

       

      I'm currently busy installing ES2 on a WAS / Windows 2003 machine which connects to an Oracle 10g DB. I've following the installation instructions quite carefully, but I ran into a brick wall that I can't seem to move myself. Hopefully someone over here can help me out.

       

      Over many attempts I've had various different issues while running the configuration manager. Most of these issues pop up after the ear files are configured and are ready to be deployed. Reviewing the log files I noticed that the I get a java.lang.OutOfMemoryError at the times when the issues pop up. The server itself doesn't have a shortage of RAM (16GB) and I did increase the deployer heap size as described in the manual.

       

      Eventually I've now given up searching and decided to throw myself at the mercy of the forums for some help . Since I don't really even know where to begin investigating the issue (besides confirming that I followed the steps in the manual), I'd be appreciative of almost any suggestions.

       

      Thanks

       

      Greg

        • 1. Re: Java.lang.OutOfMemoryError while running config manager
          JayanKandathil techies

          Greg:

           

          The OutOfMemoryExceptions are probably related to this:

          http://blogs.adobe.com/livecycle/2010/01/outofmemoryerror_on_deploying.html

           

          You seem to be beyond those now.

           

          The one recommendation I have for you is to deploy the LiveCycle EAR files to WebSphere manually, instead of letting LCM do it.  This is especially true if you're deploying to a distributed WebSphere cluster.

          • 2. Re: Java.lang.OutOfMemoryError while running config manager
            Greg @ Innisfree ZA Community Member

            Thanks for the quick response Jayan.

             

            As you've guessed I've already read most of what is available regarding the out of memory error and also followed most of the advice provided. Here's a summary of what I've done already:

             

            • Updated the heap size of the EJB deployer (Xmxto 1792M)
            • Increased the SOAP request timeout to 1800
            • Increased the transaction timeout to 600 seconds

             

            I've tried to deploy the configured ears manually, but there's a catch there as well - The ears are already deployed from a previous (uncompleted) run of the configuration manager. Until now all attempts to undeploy and redeploy with the updated ears have been unsuccessful (non-responsive or OutOfMemoryError as well)

             

            The server involved is also running EMC Documentum (in a seperate Tomcat container) and I'm concerned that the issue lies wuth the configuration of the %JAVA_HOME% environment variable which now has two values (one for tomcat and one for WAS). Could this be a potential source of problems?

             

            Regards,

            • 3. Re: Java.lang.OutOfMemoryError while running config manager
              JayanKandathil techies

              Time to go manual.  Login to WebSphere's Admin Console, undeploy the EARs and then manually deploy them.

               

              I don't know how you managed to have two values for the same environment variable (JAVA_HOME) - you must have those defined as both "user" and "system".

              • 4. Re: Java.lang.OutOfMemoryError while running config manager
                Greg @ Innisfree ZA Community Member

                Thanks Jayan

                 

                Will post back once the problem is resolved

                • 5. Re: Java.lang.OutOfMemoryError while running config manager
                  Greg @ Innisfree ZA Community Member

                  Manual deploy has not been 100% successful either, but I'm slowly progressing. I was able to undeploy the old apps with some effort. Bounced the box and then resolved the issue with the multiple JAVA_HOME environment variables. Then came the deployment of the LC ears...

                   

                  On this machine I'm trying to deploy 2 ears

                  • adobe-livecycle-native-websphere-x86_win32 (95MB)
                  • adobe-livecycle-websphere (150MB)

                   

                  The ...native... ear deploys without issues. However, when I try deploy the bigger ear I get the OutOfMemoryError.

                   

                  Since attchments are current unavailable, here is an extract from my errorLog (if it helps):

                   

                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R AppDeploymentException: [Unexpected exception processing archive file.]
                  java.lang.OutOfMemoryError: ZIP002:OutOfMemoryError, MEM_ERROR in deflate_init2
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R java.lang.OutOfMemoryError: ZIP002:OutOfMemoryError, MEM_ERROR in deflate_init2
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at java.util.zip.Deflater.init(Native Method)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at java.util.zip.Deflater.<init>(Deflater.java:148)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at java.util.zip.ZipOutputStream.<init>(ZipOutputStream.java:86)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.ZipStreamSaveStrategyImpl.<init> (ZipStreamSaveStrategyImpl.java:59)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.ZipStreamSaveStrategyImpl.create NestedSaveStrategy(ZipStreamSaveStrategyImpl.java:89)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.SaveStrategyImpl.save(SaveStrate gyImpl.java:130)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.ZipStreamSaveStrategyImpl.save(Z ipStreamSaveStrategyImpl.java:215)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.SaveStrategyImpl.save(SaveStrate gyImpl.java:143)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.SaveStrategyImpl.saveFiles(SaveS trategyImpl.java:165)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.strategy.SaveStrategyImpl.save(SaveStrate gyImpl.java:107)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.save(ArchiveImpl.java:14 98)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ModuleFileImpl.save(ModuleFileImpl.j ava:173)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.saveAsNoReopen(ArchiveIm pl.java:1630)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.saveAs(ArchiveImpl.java: 1527)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.eclipse.jst.j2ee.commonarchivecore.internal.impl.ArchiveImpl.save(ArchiveImpl.java:14 77)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.websphere.management.application.client.ArchiveDeploymentInfo.close(ArchiveDeploy mentInfo.java:398)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.websphere.management.application.client.AppDeploymentController.close(AppDeployme ntController.java:706)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.websphere.management.application.client.AppDeploymentController.saveAndClose(AppD eploymentController.java:718)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.console.appmanagement.action.AppInstallSummaryAction.execute(AppInstallSummary Action.java:124)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.apache.struts.action.RequestProcessor.processActionPerform(Unknown Source)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.apache.struts.action.RequestProcessor.process(Unknown Source)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.apache.struts.action.ActionServlet.process(Unknown Source)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at org.apache.struts.action.ActionServlet.doPost(Unknown Source)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1146)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1087)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:145)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistence(WSCUrlFilter.java:792 )
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:3 63)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:229)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java: 190)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:130)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:87)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:837)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:680)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:588)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:525)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3548)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:269)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:818)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1478)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:126)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink .java:458)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink .java:387)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.jav a:102)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLRe adServiceContext.java:1818)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionLi stener.java:165)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:196)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
                  [3/31/10 7:30:17:087 CAT] 00000020 SystemErr     R     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1497)

                  • 6. Re: Java.lang.OutOfMemoryError while running config manager
                    JayanKandathil techies

                    You need to increase the memmory settings higher for ejbdeploy.bat

                     

                    adobe-livecycle-native-websphere-x86_win32.ear would deploy fine because it contains no EJBs.  The other one does - lots of them!!

                    • 7. Re: Java.lang.OutOfMemoryError while running config manager
                      Greg @ Innisfree ZA Community Member

                      Hi Jayan

                       

                      Just a quick update on my results. After getting a WAS expert to have a look at my server he eventually proposed a reinstall of WAS. The version I was working on was ND 6.1.0.29 and it seemed to introduce unexpected issues.

                       

                      After replacing with a stand-alone WAS all was fine with no problems, well almost no problems, but nothing that belongs on this forum.

                       

                      Thanks for the help