Hi Experts,
I installed NAS 7.0 and it was working fine. Then I installed NWDI components and was configuring the environment for NWDI, which time my Java server stopped functioning. When I shut it down and restart the Java server remains yellow forever with message 'some processes running'. The developer trace for the J2EE Process->Server0 is below:
**********************************************************************
JStartupIReadSection: read node properties [ID1036750]
-> node name : server0
-> node type : server
-> node execute : yes
-> jlaunch parameters :
-> java path : C:\j2sdk1.4.2_12
-> java parameters : -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 -Djco.jarm=1 -XX:MaxPermSize=256M -XX:PermSize=256M -XX:NewSize=171M -XX:MaxNewSize=171M -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 -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> java vm version : 1.4.2_12-b03
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 512M
-> init heap size : 1024M
-> root path : C:\usr\sap\W99\JC00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : C:\usr\sap\W99\JC00\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\W99\JC00\exe\jstartup.jar;C:\usr\sap\W99\JC00\exe\jvmx.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : no
-> debug mode : no
-> debug port : 50021
-> shutdown timeout : 120000
**********************************************************************
[Thr 2860] JLaunchISetDebugMode: set debug mode [no]
[Thr 1744] JLaunchIStartFunc: Thread 1744 started as Java VM thread.
**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [server0]
-> stack : 262144 Bytes
-> arg[ 0]: exit
-> arg[ 1]: abort
-> arg[ 2]: vfprintf
-> arg[ 3]: -Djava.security.policy=./java.policy
-> arg[ 4]: -Djava.security.egd=file:/dev/urandom
-> arg[ 5]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy
-> arg[ 6]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy
-> arg[ 7]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy
-> arg[ 8]: -Djco.jarm=1
-> arg[ 9]: -XX:MaxPermSize=256M
-> arg[ 10]: -XX:PermSize=256M
-> arg[ 11]: -XX:NewSize=171M
-> arg[ 12]: -XX:MaxNewSize=171M
-> arg[ 13]: -XX:+DisableExplicitGC
-> arg[ 14]: -verbose:gc
-> arg[ 15]: -Xloggc:GC.log
-> arg[ 16]: -XX:+PrintGCDetails
-> arg[ 17]: -XX:+PrintGCTimeStamps
-> arg[ 18]: -Djava.awt.headless=true
-> arg[ 19]: -Dsun.io.useCanonCaches=false
-> arg[ 20]: -XX:SoftRefLRUPolicyMSPerMB=1
-> arg[ 21]: -XX:SurvivorRatio=2
-> arg[ 22]: -XX:TargetSurvivorRatio=90
-> arg[ 23]: -Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptor.JTSInitializer
-> arg[ 24]: -Dsys.global.dir=C:\usr\sap\W99\SYS\global
-> arg[ 25]: -Dapplication.home=C:\usr\sap\W99\JC00\exe
-> arg[ 26]: -Djava.class.path=C:\usr\sap\W99\JC00\exe\jstartup.jar;C:\usr\sap\W99\JC00\exe\jvmx.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> arg[ 27]: -Djava.library.path=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;C:\j2sdk1.4.2_12\bin;C:\usr\sap\W99\JC00\j2ee\os_libs;c:\sapdb\programs\bin;c:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_12\bin;C:\usr\sap\W99\SYS\exe\uc\NTI386
-> arg[ 28]: -Dmemory.manager=512M
-> arg[ 29]: -Xmx512M
-> arg[ 30]: -Xms1024M
-> arg[ 31]: -DLoadBalanceRestricted=no
-> arg[ 32]: -Djstartup.mode=JCONTROL
-> arg[ 33]: -Djstartup.ownProcessId=6328
-> arg[ 34]: -Djstartup.ownHardwareId=P1320342038
-> arg[ 35]: -Djstartup.whoami=server
-> arg[ 36]: -Djstartup.debuggable=no
-> arg[ 37]: -DSAPINFO=W99_00_server
-> arg[ 38]: -DSAPSTARTUP=1
-> arg[ 39]: -DSAPSYSTEM=00
-> arg[ 40]: -DSAPSYSTEMNAME=W99
-> arg[ 41]: -DSAPMYNAME=tpc-5_W99_00
-> arg[ 42]: -DSAPDBHOST=tpc-5
-> arg[ 43]: -Dj2ee.dbhost=tpc-5
**********************************************************************
Error occurred during initialization of VM
Incompatible initial and maximum heap sizes specified
[Thr 1744] JLaunchIAbortJava: abort hook is called
[Thr 1744] **********************************************************************
ERROR => The Java VM aborted unexpectedly.
Please see SAP Note 943602 , section 'Java VM crashes'
for additional information and trouble shooting.
**********************************************************************
[Thr 1744] JLaunchCloseProgram: good bye (exitcode = -2)
Now when I look into the note suggested here, it says for 7.0 MaxPermSize should be 256M and
PermSize=256M. And in the above log, if you see the arguments arg[ 9]: -XX:MaxPermSize=256M
-> arg[ 10]: -XX:PermSize=256M it satisfies the same.
It states 'Incompatible initial and maximum heap sizes specified' - in log, we can find 'heap size: 512M and init heap size: 1024M. does this 'heap size' mean max heap size?
Should we increase the heap size or decrease initial heap size? if so, how much?
and I cant use configtool.bat to increase heap size as my server is not up, so what other way to increase the heap size?
Points are obvious, but highly appreciate if anyone could help us. Thanks.
Edited by: Prasad Muthuraman on Sep 24, 2008 11:12 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.