cancel
Showing results for 
Search instead for 
Did you mean: 

JAVA memory error in JVM 4,

Former Member
0 Kudos

Hi Folks,

i am getting below java out of memory error in java system, i have 6GB memory defined, not sure what cause? , would you be able to help?

###############################################################################################################

SAP J2EE Engine Version 7.02 SP 12   PatchLevel 141257. is running! PatchLevel 141257. April 02, 2013 14:55 GMT

>47.974: [GC 47.974: [ParNew: 468442K->62641K(512000K), 0.2166430 secs] 468442K->62641K(1994752K), 0.2167800 secs] [Times: user=0.31 sys=0.0
3, real=0.22 secs]
57.683: [GC 57.684: [ParNew: 472241K->75972K(512000K), 0.0766940 secs] 472241K->75972K(1994752K), 0.0768360 secs] [Times: user=0.21 sys=0.00
, real=0.08 secs]
FATAL: Caught OutOfMemoryError! Node will exit with exit code 666java.lang.OutOfMemoryError: unable to create new native thread
        at java.lang.Thread.start0(Native Method)
        at java.lang.Thread.start(Thread.java:662)
        at com.sap.mw.jco.JCO$Server.start(JCO.java:8820)
        at com.sap.lcr.sagent.rfc.SAPProxyRfc.start(SAPProxyRfc.java:239)
        at com.sap.lcr.sagent.BridgeControl.startImpl(BridgeControl.java:325)
        at com.sap.lcr.sagent.BridgeControl.startBridge(BridgeControl.java:86)
        at com.sap.lcr.start.StartDirector.constructPermanentLcrInstances(StartDirector.java:966)
        at com.sap.lcr.start.StartDirector.getActiveStartDirector(StartDirector.java:196)
        at com.sap.lcr.cimsrv.CIMOMServlet.init(CIMOMServlet.java:131)
        at javax.servlet.GenericServlet.init(GenericServlet.java:258)
        at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
        at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java
:391)
        at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:115)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Heap
par new generation   reserved 614400K, committed 614400K, used 202077K [0x0000000004440000, 0x0000000029c40000, 0x0000000029c40000)
  eden space 409600K,  30% used [0x0000000004440000, 0x000000000bf66260, 0x000000001d440000)
  from space 102400K,  74% used [0x000000001d440000, 0x0000000021e713a0, 0x0000000023840000)
  to   space 102400K,   0% used [0x0000000023840000, 0x0000000023840000, 0x0000000029c40000)
concurrent mark-sweep generation reserved 5677056K, committed 1482752K, used 0K [0x0000000029c40000, 0x0000000084440000, 0x0000000184440000
)
concurrent-mark-sweep perm gen reserved 524288K, committed 524288K, used 91085K [0x0000000184440000, 0x00000001a4440000, 0x00000001a4440000
)
--------------------------------------------------------------------------------

###################################################################################################################

Thanks,

Dinesh

Accepted Solutions (0)

Answers (5)

Answers (5)

Reagan
Advisor
Advisor
0 Kudos

First check whether the machine has sufficient memory available to accommodate ABAP and Java.

If not there is no point adding more memory to heap as the result will be OOM.

First you need to find out the memory used by ABAP, Java and the database.

Regards

RB

Former Member
0 Kudos

Can you attach full log file?

Former Member
0 Kudos

Hi,

Can you please explain more about the functionality that this port is handling. Are you using this portal to download large reports ore pdf.

Have you seen this issue at specific time.

Thanks

Rishi Abrol

Former Member
0 Kudos

Hi Rishi,

this is SAP solution manager 7.1 SP8, its java keep getting down, we have 200+ system connected to our solution manager, and  around 400 agents,

Thanks,

DInesh

Former Member
0 Kudos

Hi,

This is wrong sizing done for your solution manager . Please check the sizing excel sheet for the solution manager.

https://websmp108.sap-ag.de/~form/handler?_APP=00200682500000002734&_EVENT=DISPLAY&_FRAME=NAVIGATION...

Thanks

Rishi abrol

former_member183107
Contributor
0 Kudos

From message we can clearly see that the Out of memory was caused by running out of memory in perm space. The perm space is located outside the heap. I would like to mention of the fact that more permanent space is needed if additional applications are deployed or the complexity of the applications grows.

Can you please check increase perm size with the java config tool on all server nodes of this system.

-XX:MaxPermSize and PermSize

Check SAP Note 710146 - How to change J2EE Engine JVM Settings.

Also compare the settings for your system with the recommendations given in note:

1603093 - "SAP JVM 4.1 parameters NetWeaver 2004 and 7.0"

Rgds,

Himanshu

Former Member
0 Kudos