Trusted Contributor.. RobertBuerger Trusted Contributor..
Trusted Contributor..
368 views

OO 10.80 - The JVM has run out of memory.

Hi experts!

The JVM sporadic runs out of memory. Do you have some advises how I can try to identify the cause of the problem? Or is there maybe a tuning of garbage collection necessary?

Here a some informations:

OS: Red Hat Enterprise Linux Server release 7.6 (Maipo), 8GB RAM, 2 CPU

JVM arguments: -Djava.endorsed.dirs=/opt/microfocus/oo/central/tomcat/endorsed
-Dcatalina.base=/opt/microfocus/oo/central/tomcat
-Dcatalina.home=/opt/microfocus/oo/central/tomcat
-Djava.io.tmpdir=/opt/microfocus/oo/central/tomcat/temp
-Doo.home=/opt/microfocus/oo/central
-Doo.lib=/opt/microfocus/oo/central/tomcat/temp
-XX:MaxPermSize=256m
-Dlog4j.configuration=file:////opt/microfocus/oo/central/conf/log4j.properties
-Djava.security.policy=/opt/microfocus/oo/central/tomcat/conf/catalina.policy
-XX:+UseCompressedOops
-XX:+UseParallelGC
-Xss1024k
-Dmgmt.url=https://HOST:8443/oo
-Djava.security.egd=file:/dev/./urandom
-Djavax.net.ssl.trustStore=/opt/microfocus/oo/central/var/security/client.truststore
-Djavax.net.ssl.trustStorePassword=PASS
-Devents.persistency=false
-Dout.buffer.max.buffer.weight=7500
-Djavax.net.ssl.keyStore=/opt/microfocus/oo/central/var/security/certificate.p12
-Djavax.net.ssl.keyStorePassword=PASS
-Djavax.net.ssl.keyStoreType=PKCS12
-Dcloudslang.worker.numberOfExecutionThreads=300
-Dcloudslang.worker.inBufferCapacity=600
-Dpython.path=/opt/microfocus/oo/central/lib/pythonlib
-XX:MaxMetaspaceSize=512m
-DCentral.UUID=UUID
-DCentral.HOSTNAME=HOSTNAME
-DCentral.login.hit.tolerance=2000
-DCentral.login.suspend=300000
-Doverride.startup.mode=LWSSO
-Djava.util.Arrays.useLegacyMergeSort=true
-Xms1024m
-Xmx4096m
-Djava.library.path=.
-Dwrapper.key=KEY
-Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000
-Dwrapper.jvm.port.max=31999
-Dwrapper.disable_console_input=TRUE
-Dwrapper.pid=28131
-Dwrapper.version=3.5.17-pro
-Dwrapper.native_library=wrapper
-Dwrapper.arch=x86
-Dwrapper.service=TRUE
-Dwrapper.cpu.timeout=10
-Dwrapper.jvmid=3
-Dwrapper.lang.domain=wrapper

 

 

 

And here are the errors in wrapper.log:

STATUS | wrapper | 2018/11/30 14:12:29 | Pinging the JVM took 82 seconds to respond.
STATUS | wrapper | 2018/11/30 14:12:29 | Pinging the JVM took 73 seconds to respond.
STATUS | wrapper | 2018/11/30 14:12:29 | Pinging the JVM took 64 seconds to respond.
STATUS | wrapper | 2018/11/30 14:12:29 | Pinging the JVM took 55 seconds to respond.
STATUS | wrapper | 2018/11/30 14:12:29 | Pinging the JVM took 46 seconds to respond.
INFO | jvm 1 | 2018/11/30 14:14:19 | Exception in thread "local-scheduler-persisted_QuartzSchedulerThread" java.lang.OutOfMemoryError: GC overhead limit exceeded
STATUS | wrapper | 2018/11/30 14:14:19 | The JVM has run out of memory. Restarting JVM.
INFO | jvm 1 | 2018/11/30 14:14:19 | at java.lang.reflect.Method.copy(Method.java:153)
INFO | jvm 1 | 2018/11/30 14:14:19 | at java.lang.reflect.ReflectAccess.copyMethod(ReflectAccess.java:140)
INFO | jvm 1 | 2018/11/30 14:14:19 | at sun.reflect.ReflectionFactory.copyMethod(ReflectionFactory.java:316)
INFO | jvm 1 | 2018/11/30 14:14:19 | at java.lang.Class.copyMethods(Class.java:3124)
INFO | jvm 1 | 2018/11/30 14:14:19 | at java.lang.Class.getMethods(Class.java:1615)
INFO | jvm 1 | 2018/11/30 14:14:19 | at java.beans.MethodRef.find(MethodRef.java:77)
INFO | jvm 1 | 2018/11/30 14:14:19 | at java.beans.MethodRef.get(MethodRef.java:62)
INFO | jvm 1 | 2018/11/30 14:14:19 | at java.beans.PropertyDescriptor.getWriteMethod(PropertyDescriptor.java:271)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.Util.getSetMethod(Util.java:171)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.Util.setBeanProps(Util.java:146)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.setTriggerStateProperties(StdJDBCDelegate.java:1875)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectTrigger(StdJDBCDelegate.java:1849)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1531)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:2808)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:2759)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.JobStoreSupport$40.execute(JobStoreSupport.java:2757)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.JobStoreSupport.executeInNonManagedTXLock(JobStoreSupport.java:3799)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTriggers(JobStoreSupport.java:2756)
INFO | jvm 1 | 2018/11/30 14:14:19 | at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:272)
INFO | jvm 1 | 2018/11/30 14:14:19 | Nov 30, 2018 2:14:18 PM org.apache.tomcat.util.net.NioEndpoint$SocketProcessor doRun
INFO | jvm 1 | 2018/11/30 14:14:19 | SEVERE:
INFO | jvm 1 | 2018/11/30 14:14:19 | java.lang.OutOfMemoryError: GC overhead limit exceeded
STATUS | wrapper | 2018/11/30 14:14:19 | The JVM has run out of memory. Restarting JVM.
INFO | jvm 1 | 2018/11/30 14:14:19 |
STATUS | wrapper | 2018/11/30 14:14:19 | Pinging the JVM took 53 seconds to respond.
INFO | jvm 1 | 2018/11/30 14:14:19 | Nov 30, 2018 2:14:19 PM org.apache.catalina.core.StandardWrapperValve invoke
INFO | jvm 1 | 2018/11/30 14:14:19 | SEVERE: Servlet.service() for servlet [rest] in context with path [/oo] threw exception [Handler processing failed; nested exception is java.lang.OutOfMemoryError: GC overhead limit exceeded] with root cause
STATUS | wrapper | 2018/11/30 14:14:19 | The JVM has run out of memory. Restarting JVM.
INFO | jvm 1 | 2018/11/30 14:14:19 | java.lang.OutOfMemoryError: GC overhead limit exceeded
STATUS | wrapper | 2018/11/30 14:14:19 | The JVM has run out of memory. Restarting JVM.

 

Many thanks for your help!

Cheers!

Robert

 

0 Likes
1 Reply
Micro Focus Expert
Micro Focus Expert

Re: OO 10.80 - The JVM has run out of memory.

Hello Robert,

 

Thank you for contacting Micro Focus Forum.

My name is Carlos, I am from the OO/CSA team.

 

A good start point to troubleshoot is to check if any heap dump is being created. Please make sure the wrapper.java.additional.7=-XX:+HeapDumpOnOutOfMemoryError is set in the central-wrapper.conf file and if a heap dump is created, the you can use a tool to inspect it like JVisualVM that comes with the JDK.

 

Thanks;

Regards! 

Carlos Rojas
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.