Skip to Content
0
Former Member
Dec 16, 2004 at 02:38 AM

Install EP60 SP3 - J2EE server won't start up????

34 Views

I am following the manual 'installation of sap enterprise portal on web as 6.40' installation sequence for installing the netweaver 04 EP60 portal. (pg 8). The following steps were ok

1. install web as 6.4 engine sp3.

2. upgrade sap web as 6.4 j2ee engine sp3 to sp4.

The next step is to install the portal platform EP60 sp3. When I started this install, the sapinst failed when it tried to restart the J2EE engine. Now I can't get the engine to start using MMC. The following is the developer trace file;

Wed Dec 15 21:26:42 2004

  • ERROR => JStartupFixMemSize: Bad memory size unit in 400 (neither K, M, of G - assuming M [jstartxx.c 1822]

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

JStartupIReadSection: read node properties [ID19615050]

-> node name : server0

-> node type : server

-> java path : D:\j2sdk1.4.2_06

-> 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=512M -XX:MaxNewSize=1024M -XX:NewRatio=3 -XX:+DisableExplicitGC -XX:MaxPermSize=128M -XX:PermSize=128M

-> java vm version : 1.4.2_06-b03

-> java vm vendor : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)

-> java vm type : server

-> java vm cpu : x86

-> heap size : 400M

-> init heap size : 512M

-> root path : D:\usr\sap\RSP\JC01\j2ee\cluster\server0

-> class path : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> OS libs path : D:\usr\sap\RSP\JC01\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 : D:\usr\sap\RSP\JC01\j2ee\os_libs\jstartup.jar

-> shutdown class : com.sap.engine.boot.Start

-> parameters :

-> debuggable : yes

-> debug mode : no

-> debug port : 50121

-> shutdown timeout: 10000

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

JLaunchISetDebugMode: set debug mode [no]

JLaunchIStartFunc: Thread 3972 started as Java VM thread.

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

JHVM_LoadJavaVM: VM Arguments of node [server0]

-> stack : 262144 Bytes

-> arg[ 0]: exit

-> arg[ 1]: abort

-> arg[ 2]: -Djava.security.policy=./java.policy

-> arg[ 3]: -Djava.security.egd=file:/dev/urandom

-> arg[ 4]: -Dorg.omg.CORBA.ORBClass=com.sap.engine.system.ORBProxy

-> arg[ 5]: -Dorg.omg.CORBA.ORBSingletonClass=com.sap.engine.system.ORBSingletonProxy

-> arg[ 6]: -Djavax.rmi.CORBA.PortableRemoteObjectClass=com.sap.engine.system.PortableRemoteObjectProxy

-> arg[ 7]: -XX:NewSize=512M

-> arg[ 8]: -XX:MaxNewSize=1024M

-> arg[ 9]: -XX:NewRatio=3

-> arg[ 10]: -XX:+DisableExplicitGC

-> arg[ 11]: -XX:MaxPermSize=128M

-> arg[ 12]: -XX:PermSize=128M

-> arg[ 13]: -Dsys.global.dir=D:\usr\sap\RSP\SYS\global

-> arg[ 14]: -Dapplication.home=D:\usr\sap\RSP\JC01\j2ee\os_libs

-> arg[ 15]: -Djava.class.path=D:\usr\sap\RSP\JC01\j2ee\os_libs\jstartup.jar;.\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.

-> arg[ 16]: -Djava.library.path=D:\j2sdk1.4.2_06\jre\bin\server;D:\j2sdk1.4.2_06\jre\bin;D:\j2sdk1.4.2_06\bin;D:\usr\sap\RSP\JC01\j2ee\os_libs;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;D:\jdk1.3.1_11\bin;C:\Resource Kit\;C:\Program Files\Common Files\Network Associates\VirusScan Engine\4.0.xx\;C:\NetIQ\AppManager\bin;C:\NetIQ\Common\bin;C:\Program Files\Support Tools\;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;D:\j2sdk1.4.2_06\bin;D:\usr\sap\RSP\SCS00\exe;D:\usr\sap\RSP\JC01\exe;D:\usr\sap\RSP\SYS\exe\run

-> arg[ 17]: -Dmemory.manager=400M

-> arg[ 18]: -Xmx400M

-> arg[ 19]: -Xms512M

-> arg[ 20]: -DLoadBalanceRestricted=no

-> arg[ 21]: -Djstartup.mode=JCONTROL

-> arg[ 22]: -Djstartup.ownProcessId=4664

-> arg[ 23]: -Djstartup.ownHardwareId=F1345088347

-> arg[ 24]: -Djstartup.whoami=server

-> arg[ 25]: -Djstartup.debuggable=yes

-> arg[ 26]: -DSAPSTARTUP=1

-> arg[ 27]: -DSAPSYSTEM=01

-> arg[ 28]: -DSAPSYSTEMNAME=RSP

-> arg[ 29]: -DSAPMYNAME=NCSUSRASAPR04_RSP_01

-> arg[ 30]: -DSAPDBHOST=

-> arg[ 31]: -Dj2ee.dbhost=ncsusrasapr04

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

JLaunchIAbortJava: abort hook is called

JLaunchCloseProgram: good bye (exitcode=-2)

Is this a memory problem? If so, what should I be coding in?

Thanks

Rich Allen