Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Having trouble in restarting the SAP instance

Hi Experts,

I've restarted our sap system in sapmmc and we've noticed that under j2ee process > sdm (green) > dispatcher (green) > server 0 (yellow) with the status of Starting apps. it has been more than an hour and the status is still startiing apps.

I've checked the developer trace of server 0:

.

.

.

.

.

Thu Jun 09 14:41:46 2011

Desired survivor size 32145408 bytes, new threshold 4 (max 31)

- age 1: 12451272 bytes, 12451272 total

- age 2: 12065592 bytes, 24516864 total

- age 3: 4301064 bytes, 28817928 total

- age 4: 6653504 bytes, 35471432 total

Thu Jun 09 14:46:11 2011

Desired survivor size 32145408 bytes, new threshold 4 (max 31)

- age 1: 8820536 bytes, 8820536 total

- age 2: 10923432 bytes, 19743968 total

- age 3: 11550192 bytes, 31294160 total

- age 4: 4192328 bytes, 35486488 total

Thu Jun 09 15:26:46 2011

Desired survivor size 32145408 bytes, new threshold 4 (max 31)

- age 1: 7963392 bytes, 7963392 total

- age 2: 4799528 bytes, 12762920 total

- age 3: 10711912 bytes, 23474832 total

- age 4: 11155592 bytes, 34630424 total

Why is this happening? i don't know if this will up or not? but based on our experience if the status is "Starting apps" it will surely UP. but we've waited too long and still it doesn't UP. Please help.

to give you an overview. we are using Microsoft Windows Server 2003 x64, 16GB ram.

Also, i've checked the parameters in configtool

-> instance_ID27168

> dispatcher_ID2716800

> server_ID2716850

dispatcher_ID2716800

>max heap size (MB): 170

>java parameters:

-XX:NewSize=57M

-XX:MaxNewSize=57M

-Xms170M

-XX:+DisableExplicitGC

-verbose:gc

-Xloggc:GC.log

-Djava.security.policy=.\java.policy

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

-Djco.jarm=1

server_ID2716850

>max heap size (MB): 2048

-Djco.jarm=1

-XX:MaxPermSize=1200M

-XX:PermSize=1200M

-Xms2048M

-Xmx2048M

-XX:NewSize=341M

-XX:MaxNewSize=341M

-XX:+DisableExplicitGC

-verbose:gc

-Xloggc:GC.log

-XX:+PrintGCDetails

-XX:+PrintGCTimeStamps

-Djava.awt.headless=true

-Dsun.io.useCanonCaches=false

-XX:SoftRefLRUPolicyMSPerMB=1

-XX:SurvivorRatio=8

-XX:TargetSurvivorRatio=90

-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

-Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-XX:+UseParNewGC

-XX:+PrintTenuringDistribution

-XX:+UseTLAB

-XX:+HandlePromotionFailure

-XX:+PrintClassHistogram

-XX:+HeapDumpOnOutOfMemoryError

-Xss2m

Please let me know if you have any documents or suggestions pertaining to these parameters and reason for taking too long to UP the system..

Thanks,

Tony

Former Member
Not what you were looking for? View more on this topic or Ask a question