3 Replies Latest reply on Apr 19, 2018 10:06 AM by fresh-it

    Java memory error

    fresh-it

      Hello,

       

      We've started getting an errror stating: "java.lang.OutOfMemoryError: Java heap space". I've tried to increase the JVM using instructions from this article, but it doesn't help. I've also read that clearing the JVM heap memory could help and this is done by restarting, but even after restarting we get the error after 5-10 minutes of use.

       

      Below is the stack trace, any help is greatly appreciated. We're running WHD version 12.1.0.300

       

      We're sorry, an unexpected error occurred:

      java.lang.OutOfMemoryError: Java heap space

      A bug report has been e-mailed to SolarWinds.

       

      Submit

      Submit Stack Trace

       

      java.lang.OutOfMemoryError: Java heap space

           at java.util.Arrays.copyOf(Unknown Source)

           at java.lang.AbstractStringBuilder.expandCapacity(Unknown Source)

           at java.lang.AbstractStringBuilder.append(Unknown Source)

           at java.lang.StringBuffer.append(Unknown Source)

           at org.apache.log4j.helpers.PatternParser$LiteralPatternConverter.format(PatternParser.java:419)

           at org.apache.log4j.PatternLayout.format(PatternLayout.java:506)

           at org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:310)

           at org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.java:276)

           at org.apache.log4j.WriterAppender.append(WriterAppender.java:162)

           at org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)

           at org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)

           at org.apache.log4j.Category.callAppenders(Category.java:206)

           at org.apache.log4j.Category.forcedLog(Category.java:391)

           at org.apache.log4j.Category.error(Category.java:305)

           at er.extensions.eof.ERXEOAccessUtilities.isOptimisticLockingFailure(ERXEOAccessUtilities.java:841)

           at er.extensions.eof.ERXEC._saveChanges(ERXEC.java:1100)

           at er.extensions.eof.ERXEC.saveChanges(ERXEC.java:1016)

           at com.macsdesign.whd.ui.SessionManager.removeOldLingeringSessionsForSubscriber(SessionManager.java:206)

           at com.macsdesign.whd.ui.TicketListPage.searchTickets(TicketListPage.java:1282)

           at com.macsdesign.whd.ui.TicketQualifierBuilder.qualifier(TicketQualifierBuilder.java:113)

           at com.macsdesign.whd.ui.TicketQualifierBuilder.appendToResponse(TicketQualifierBuilder.java:49)

           at com.webobjects.appserver._private.WOComponentReference.appendToResponse(WOComponentReference.java:135)

           at com.webobjects.appserver._private.WODynamicGroup.appendChildrenToResponse(WODynamicGroup.java:126)

           at com.webobjects.appserver._private.WODynamicGroup.appendToResponse(WODynamicGroup.java:136)

           at com.webobjects.appserver._private.WOComponentContent.appendToResponse(WOComponentContent.java:51)

           at com.webobjects.appserver._private.WODynamicGroup.appendChildrenToResponse(WODynamicGroup.java:126)

           at com.webobjects.appserver._private.WOConditional.appendToResponse(WOConditional.java:94)

           at com.webobjects.appserver._private.WODynamicGroup.appendChildrenToResponse(WODynamicGroup.java:126)

           at com.webobjects.appserver._private.WODynamicGroup.appendToResponse(WODynamicGroup.java:136)

           at com.webobjects.appserver.WOComponent.appendToResponse(WOComponent.java:1122)

           at com.webobjects.appserver._private.WOComponentReference.appendToResponse(WOComponentReference.java:135)

           at com.webobjects.appserver._private.WODynamicGroup.appendChildrenToResponse(WODynamicGroup.java:126)

        • Re: Java memory error
          typhoon87

          If this is a sudden and new issue and there have been no major changes to your environment otherwise and your sure the server or VM itself is not out of memory you should probably open a ticket with SolarWinds support. Also please note 12.1 is no longer supported and 12.2 is only supported until November of 2018 so an upgrade to at least 12.3 or higher may be necessary.

          1 of 1 people found this helpful
          • Re: Java memory error
            comtcjm

            It's worth disabling any new Action Rules, Tasks, AD/LDAP Syncs, Asset Discovery Sync etc, as these could be hogging memory / creating an internal loop.

             

            Check your logs to see if there is anything easy to spot that could be the problem.

             

            Also upgrade to the 64-bit version of WHD if you already haven't.

             

            regards

            Chris