Maxpermsize for Solman 7.1

[Former Member]

Hi,

We refreshed our development Solman from production, essentially a database refresh/rename and a JAVA import. For the JAVA import we used the install kit for Solution Manager 7.1 SPS 04. After the upgrade server0 fails to start with the following error:

[Full GC 37649K->37641K(1604672K), 0.6047320 secs]

FATAL: Caught OutOfMemoryError! Node will exit with exit code 666java.lang.OutOfMemoryError: PermGen space[GC 37918K->37673K(

1604800K), 0.0059190 secs]

We've confirmed that the development system had the same Java memory parameters as production, which worked. Based on the error I assume that MaxPermSize needs to be increased. I have increased Max Heap Size to 2048 from 256 and similarly increased both MaxPermSize and PermSize. We still get the same failure.

Here are the current Java parameters on the instance:

-Xms2048M

-Xss2M

-XX:MaxNewSize=341M

-XX:NewSize=341M

-XX:MaxPermSize=2048M

-XX:PermSize=2048M

-XX:CompilerThreadStackSize=4096

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:+HandlePromotionFailure

-XX:+DisableExplicitGC

-XX:+HeapDumpOnOutOfMemoryError

-XX:HeapDumpPath=OOM.hprof

-XX:+UseConcMarkSweepGC

-XX:+UseTLAB

-XX:+PrintGCTimeStamps

-XX:+PrintGCDetails

-verbose:gc

-Dsun.io.useCanonCaches=false

-Djava.awt.headless=true

-Djco.jarm=1

-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

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

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

Is there any documentation on the Java memory requirements for Solman 7.1? I have already gone through the install doc, upgrade doc, configuration doc, OSS notes, and SDN without finding anything.

I know the JAVA import introduced several differences such as the JAVA_HOME now points to

/usr/sap/<SID>/DVEBMGS00/exe/sapjvm_4. The production system is an upgrade from an earlier version of Solution Manager, not a new install.

Thanks,

Russ

[nicholas_chang · Accepted solution]

Hi Russ,

What;s the physical memory on your Prod box and Dev Box?

Could you please check is there memory bottleneck on your Dev box?

[Former Member · Accepted solution]

Hi Nicholas,

Thanks for the response.

Both systems have 12 GB of memory. I don't see any paging on either system.

I've restarted the system multiple times, cleaning ipcs each time. I have rebooted the box. I have stopped OEM, SMD, and wily.

No joy.

[Former Member]

Hi,

if you sure of both dev and Prd same settings, then

can we try this, just execute cleanibc all

and start the system. if not once reboot the server and start the system.

check the note too Note 1248926

Please update.

Thanks,

Jansi

[Former Member]

Hi Jansi,

Thank you for the reply.

Both systems have the same amount of physical memory.

The settings were originally identical, presumably due to the Java refresh from a Java export of production taken two weeks ago. I have subsequently increased the settings for max heap size, maxpermsize, and permsize in an attempt to get JAVA to start.

I have restarted the system multiple times, cleaning ipcs each time with either cleanipc or ipcrm.

I have rebooted the box.

I have reviewed note 1248926 and am currently reviewing note 723909.