cancel
Showing results for 
Search instead for 
Did you mean: 

jlaunch.exe consuming more memory !

anand_sampath2
Participant
0 Kudos

Hello,

I am in to the system preparation phase in solution manager . When i tried to sync up SLD and LMDB, jlaunch.exe starts consuming more memory which i checked in the task manager and also in resource monitor because of that the system lags its responsiveness .This same thing happened for our previous solman server which had 4GB RAM so we thought because of the ram we had this issue so we scraped it out and installed a fresh solman server with 8GB RAM but now also we are facing  the same issue.            

The following are the java parameters:

> java parameters 

-XX:MaxNewSize=600M

-XX:NewSize=600M

-XX:MaxPermSize=512M

-XX:PermSize=512M

-XX:+UseConcMarkSweepGC

-XX:+DisableExplicitGC

-XX:TargetSurvivorRatio=90

-XX:SurvivorRatio=4

-XX:+PrintGCDetails

-XX:+PrintGCTimeStamps

-verbose:gc

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:HeapDumpPath=OOM.hprof

-XX:+HeapDumpOnOutOfMemoryError

-Djco.jarm=1 -Djava.awt.headless=true

-Djava.security.policy=./java.policy

-Djava.security.egd=file:/dev/urandom

-Dsun.io.useCanonCaches=false

-Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-Dcom.sap.jvm.scenario=j2ee

java vm version    : 4.1.016 1.6-b03

-> java vm vendor     : SAP Java Server VM (SAP AG)

-> java vm type       : server

-> java vm cpu        : amd64

-> heap size          : 2048M

-> init heap size     : 2048M

-> stack size         : 2M

-> root path          : C:\usr\sap\EGS\DVEBMGS00\j2ee\cluster\server0

-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> OS libs path       : C:\usr\sap\EGS\DVEBMGS00\j2ee\os_libs

-> main class         : com.sap.engine.boot.Start

-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path     : C:\usr\sap\EGS\DVEBMGS00\exe\jstartup.jar;C:\usr\sap\EGS\DVEBMGS00\exe\jvmx.jar

-> shutdown class     : com.sap.engine.boot.Start

-> parameters         :

-> debuggable         : no

-> debug mode         : no

-> debug port         : 50021

-> shutdown timeout   : 120 sec.

Can anyone help me in fixing this issue.

Thanks,

Satheesh E

Accepted Solutions (0)

Answers (1)

Answers (1)

ACE-SAP
Active Contributor
0 Kudos

Hello,

8 Gb is the strict minimum for solman itself, but your OS needs also at least 2Gb and maybe your DB is running on the same host and consume few Gb also...

Thus I would say the minimum RAM should be 12 Gb (8 for solman, 2 for Db 2 for OS)

Regards

Extract from SAP Solution Manager 7.1 Sizing Guide