OSM WebLogic Server Crashed With Error: Java.lang.OutOfMemoryError: Java Heap Space GC Overhead Limit Exceeded

(Doc ID 1361920.1)

Last updated on NOVEMBER 08, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.6 to 10.3.6
Oracle Communications Order and Service Management - Version 7.0.2 and later
Information in this document applies to any platform.
***Checked for relevance on 23-APR-2013***
***Checked for relevance on 24-Spet-2014***
***Checked for relevance on 25-Feb-2016***
***Checked for relevance on 08-Nov-2017***

Symptoms

OSM WLS Server is started with heap setting of "-Xms2000m -Xmx2000m -Xmn800m -XX:PermSize=128m -XX:MaxPermSize=512m -verbose:gc".

OSM WebLogic Server repetitively crashes.

Most of time that we deploy or search an order in OSM GUI, the Application Server generates a series of errors like this:

<Sep 15, 2011 5:18:37 AM CDT> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
java.lang.OutOfMemoryError: Java heap space.
java.lang.OutOfMemoryError: Java heap space
>
Exception in thread "[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: Java heap space
<Sep 15, 2011 5:19:07 AM CDT> <Error> <netuix> <BEA-423405> <An exception [java.lang.OutOfMemoryError: Java heap space] was thrown while rendering the content at [/jsp/breadcrumb/index.jsp].
javax.servlet.ServletException: java.lang.OutOfMemoryError: Java heap space
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:333)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.RequestDispatcherImpl.invokeServlet(RequestDispatcherImpl.java:502)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:429)
at com.bea.netuix.servlets.controls.content.JspContent.beginRender(JspContent.java:552)
Truncated. see log file for complete stacktrace
java.lang.OutOfMemoryError: Java heap space
>

Exception in thread "Timer-16" java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.io.ObjectStreamClass.getReflector(ObjectStreamClass.java:2067)
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:602)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1583)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at weblogic.rmi.extensions.server.CBVInputStream.readObject(CBVInputStream.java:64)
at weblogic.rmi.internal.ServerRequest.copy(ServerRequest.java:261)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:166)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222)
at com.mslv.oms.security.base.OMSController_h9cupp_EOImpl_1031_WLStub.isModelUpdateBeyond(Unknown Source)
at oracle.communications.ordermanagement.automation.plugin.ScriptPluginImplementationFactoy.b(Unknown Source)
at oracle.communications.ordermanagement.automation.plugin.f.run(Unknown Source)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Exception in thread "Timer-24" java.lang.OutOfMemoryError: GC overhead limit exceeded
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:205)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:222)
at com.mslv.oms.security.base.OMSController_h9cupp_EOImpl_1031_WLStub.remove(Unknown Source)
at oracle.communications.ordermanagement.automation.plugin.ScriptPluginImplementationFactoy.b(Unknown Source)
at oracle.communications.ordermanagement.automation.plugin.f.run(Unknown Source)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms