on 07-26-2004 2:13 AM
I have installed Web AS 6.40 Sneak Preview, and all is running ok. However, it appears that something automatically shuts down all tasks in the J2E instance 0 periodically.
I examined the Syslog from the SAPMMC console, and in there I found these entries:
Sun Jul 25 19:52:19 2004
ERROR => JStartupFixMemSize: Bad memory size unit in 256 (neither K, M, of G - assuming M [jstartxx.c 1822]
**********************************************************************
JStartupIReadSection: read node properties [ID8257450]
-> node name : server0
-> node type : server
-> java path : C:\j2sdk1.4.2_04
-> 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 -XX:NewSize=32m -XX:MaxNewSize=64m -XX:NewRatio=3 -XX:+DisableExplicitGC -XX:MaxPermSize=128m -Drdbms.driverLocation=C:/sapdb/programs/runtime/jar/sapdbc.jar -Dsys.global.dir=C:/usr/sap/J2E/SYS/global/
-> java vm version : 1.4.2_04-b05
-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type : server
-> java vm cpu : x86
-> heap size : 256M
-> init heap size : 128M
-> root path : C:\usr\sap\J2E\JC00\j2ee\cluster\server0
-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path : C:\usr\sap\J2E\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\J2E\JC00\j2ee\os_libs\jstartup.jar
-> shutdown class : com.sap.engine.boot.Start
-> parameters :
-> debuggable : yes
-> debug mode : no
-> debug port : 50021
-> shutdown timeout: 10000
**********************************************************************
I notice that there is a "shutdown timeout" parameter, and it's set to 10000 (don't know what the units are).
Could this parameter setting be what's causing my problem? How can I set the J2E instance up so that it won't, on its own, stop? I've looked at the Visual Administrator, but being new to all of that, didn't see anything that I cared to change without expert advice!
Thanks.
I had the same problem and it was because I've made some changes in the JRE (I replaced some jars); of course, I've solved it, restoring the JRE.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I believe that is a problem with memory settings.
Try setting the memory to 512MB. 256 MB is default setting.
I believe this should solve your problem.
Mark this question as answered if this solves your problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm told that this may be ahppening because of an expired Sneak Preview license.
If this is true, then can I uninstall the Sneak Preview, reinstall and get another 90 days?
What if I don't uninstall/reinstall - can I continue to operate (but suffer the periodic shutdown of instance 0?
Are there any caveats, tips, tricks to uninstallation/reinstallation? (I ask this, becuase the original installation was a painful process, due to conflicts with a concurretnly installed Was 6.20 Test Drive SAPDB.)
And lastly, if I uninstall, do I also have to uninstall NetWeaver Dev. Studio?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
From my experience, having the server shut down every 30 minutes renders it pretty much unusable. On our systems, a fresh install of the WAS ( after removing the old one ) did gave us 90 fresh days to try out the WAS.
I would recommend running the UNINSTSAP.EXE program under C:\usr\sap\J2E\JC00 to do the uninstall, which does a magnificent job of wiping clean the previous install. Always remember to restart.
Netweaver Dev. Studio does not seem to be affected by the licensing issue, so I wouldn't bother uninstalling it.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.