Server0 stooped when I try to start the system...

Question

Hi gurus,
I don´t know what´s happen when I try to start the system and the Java side don´t start, it stay in MMC console with yellow semaphore at disp+work.EXE and when I look inside of J2EE Process Table in the same console the server0 is stopped and it show the exit code -11113 !!
I checked two logfiles:
dev_server0 :
Sun Aug 23 21:42:48 2009
14.537: [GC 14.537: DefNew: 103014K->17353K(131328K), 0.0753503 secs 103014K->17353K(1004800K), 0.0754636 secs]
Sun Aug 23 21:42:50 2009
16.592: [GC 16.592: DefNew: 104905K->18569K(131328K), 0.0589135 secs 104905K->18569K(1004800K), 0.0590141 secs]
Sun Aug 23 21:42:53 2009
JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
19.422: [GC 19.423: DefNew: 106121K->25119K(131328K), 0.0994074 secs 106121K->25119K(1004800K), 0.0995054 secs]
JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
Sun Aug 23 21:42:54 2009
JLaunchIExitJava: exit hook is called (rc = -11113)
ERROR => The Java VM terminated with a non-zero exit code.
Please see SAP Note 943602 , section 'J2EE Engine exit codes'
for additional information and trouble shooting.
JLaunchCloseProgram: good bye (exitcode = -11113)
dev_disp:
DpJ2eeStart: j2ee state = STARTED
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1)
***LOG Q0K=> DpMsAttach, mscon ( sapssm)
DpStartStopMsg: send start message (myname is >sapssm_SSM_00                           <)
DpStartStopMsg: start msg sent
Sun Aug 23 21:40:24 2009
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
Sun Aug 23 21:40:25 2009
CCMS: Checking Downtime Configuration of Monitoring Segment.
CCMS: start to initalize 3.X shared alert area (first segment).
DpJ2eeLogin: j2ee state = CONNECTED
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet
DpMsgAdmin: Set patchno for this platform to 201
Release check o.K.
Sun Aug 23 21:40:38 2009
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE

Answer 1

Hi Arun Singh,
I´m not change any UME parameter. I checked that in fact J2EE_Guest was locked, I already unlocked this user! But I think that is not the problem, because I checked in other systems and in all of them this user is blocked, so don´t seem this is the problem!
The following are server VM settings:
-Djco.jarm=1
-XX:MaxPermSize=256M
-XX:PermSize=256M
-Xms1024M
-XX:NewSize=171M
-XX:MaxNewSize=171M
-XX:+DisableExplicitGC
-verbose:gc
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-Djava.awt.headless=true
-Dsun.io.useCanonCaches=false
-XX:SoftRefLRUPolicyMSPerMB=1
-XX:SurvivorRatio=2
-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
Answering to your second question in fact the system have the license out of date! But at two weeks ago the license was in the same state (out of date) and the java side on system was fine!!!...
Best regards,
João Dimas