Skip to Content
0
Former Member
Feb 21, 2011 at 11:34 AM

EP server nodes restarting

259 Views

Dear Gurus,

We are using NW2004s EP7.0 system on SP21. Kernel is Release700 SP236

We were experiencing java performance issue and the system was dead slow in its response.

Initially we had single server node with Heap size of 1GB.

To deal with the problem we added two more Java server nodes and assigned 1280MB and 1536MB respectively.

Since then the server is running fine but the nodes 2 and 3 are restarting very frequently.

Idx

Name

PID

State

Error

Restart

---






0

dispatcher

7494

Running

0

yes

1

server0

7495

Running

0

yes

2

server1

29075

Starting

1

yes

3

server2

29268

Starting

0

yes

4

SDM

7498

Running

0

yes

-


As far as I know heap memory is reason that can cause the node to restart due to insufficient memory.

To deal with any possible java I copied all the parameters from node1 to node2 and node three.

Please check below the node properties of the restarting nodes..

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

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

-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

-Djco.jarm=1

-XX:MaxPermSize=512M

-XX:PermSize=512M

-Xmx1536m

-Xms1536M

-XX:NewSize=307M

-XX:MaxNewSize=307M

-XX:+DisableExplicitGC

-verbose:gc

-Xloggc:GC.log

-XX:+PrintGCDetails

-XX:+PrintGCTimeStamps

-Djava.awt.headless=true

-Dsun.io.useCanonCaches=false

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:SurvivorRatio=2

-XX:TargetSurvivorRatio=90

-XX:+UseParNewGC

-XX:+PrintClassHistogram

-XX:ReservedCodeCacheSize=64M

-XX:CodeCacheMinimumFreeSpace=2M

*********************************************

I am not able to find any satisfactory log entries in thread dump trace/default logs.

This is happening every 1/2 an hour.

Please suggest.

Regards

Vishal