on 02-14-2005 8:34 PM
I have made a simple installation of the Java Web AS.
I have a HP Compaq nc6000 laptop, with 2GB RAM and Windows XP, SP1.
I installed directly from my DVDs for "SAP NetWeaver '04 SR1" (i.e. SP9) and chose "Default Installation - Java System".
I accepted all Default Values and the installation went smooth, except for starting the Java Server.
I tried to reinstall everything, to no avail.
I have searched Notes and the SDN forums, but I haven't found any answer that I can use. Please help.
This is the last log in Developer Trace
(
PCSTO210\saploc\J2E\JC00\work\dev_jcontrol)
**********************************************************************
JStartupStartJLaunch: program = C:usrsapJ2EJC00/j2ee/os_libs/jlaunch.exe
-> arg[00] = C:usrsapJ2EJC00/j2ee/os_libs/jlaunch.exe
-> arg[01] = pf=C:usrsapJ2ESYSprofileJ2E_JC00_PCSTO210
-> arg[02] = -DSAPINFO=J2E_00_bootstrap
-> arg[03] = -file=C:usrsapJ2EJC00j2eeclusterinstance.properties
-> arg[04] = -nodeName=bootstrap_ID4250850
-> arg[05] = -nodeId=-1
-> arg[06] = -syncSem=JSTARTUP_WAIT_ON_3148
-> arg[07] = -jvmOutFile=C:usrsapJ2EJC00workjvm_bootstrap_ID4250850.out
-> arg[08] = -stdOutFile=C:usrsapJ2EJC00workstd_bootstrap_ID4250850.out
-> arg[09] = -locOutFile=C:usrsapJ2EJC00workdev_bootstrap_ID4250850
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=C:usrsapJ2ESYSprofileJ2E_JC00_PCSTO210
-> lib path = PATH=C:j2sdk1.4.2_07jrebinserver;C:j2sdk1.4.2_07jrebin;c:sapdbprogramsbin;c:sapdbprogramspgm;C:PROGRA~1SECUDESECUDE~1;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:Program FilesSymantecpcAnywhere;C:Program FilesIXOSIXOS-eCONtextbin;;C:Program FilesIXOSIXOS-eCONtextoptORAbin;C:j2sdk1.4.2_07bin;C:usrsapJ2ESCS01exe;C:usrsapJ2EJC00exe;C:usrsapJ2ESYSexerun
-> exe path = PATH=C:j2sdk1.4.2_07bin;C:usrsapJ2EJC00j2eeos_libs;c:sapdbprogramsbin;c:sapdbprogramspgm;C:PROGRA~1SECUDESECUDE~1;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:Program FilesSymantecpcAnywhere;C:Program FilesIXOSIXOS-eCONtextbin;;C:Program FilesIXOSIXOS-eCONtextoptORAbin;C:j2sdk1.4.2_07bin;C:usrsapJ2ESCS01exe;C:usrsapJ2EJC00exe;C:usrsapJ2ESYSexerun
**********************************************************************
[Thr 648] Mon Feb 14 20:32:56 2005
[Thr 648] *** ERROR => invalid return code of process [bootstrap_ID4250850] (exitcode=-2) [jstartxx.c 1433]
[Thr 648] JControlExecuteBootstrap: error executing bootstrap node [bootstrap_ID4250850] (rc=-2)
[Thr 648] JControlCloseProgram: started (exitcode = -2)
[Thr 648] JControlCloseProgram: good bye... (exitcode=-2)
More trace that might be of interest:
---------------------------------------------------
trc file: "C:usrsapJ2EJC00workdev_jcmon", trc level: 1, release: "640"
---------------------------------------------------
node name : jcmon
pid : 2148
system name : J2E
system nr. : 00
started at : Mon Feb 14 20:49:55 2005
arguments :
arg[00] : C:usrsap/J2E/JC00/j2ee/os_libs/jcmon.exe
arg[01] : pf=C:usrsapJ2ESYSprofile/J2E_JC00_PCSTO210
**********************************************************************
JStartupReadInstanceProperties: read instance properties [C:usrsapJ2EJC00j2eeclusterinstance.properties;C:usrsapJ2EJC00SDMprogramconfigsdm_jstartup.properties]
-> ms host : PCSTO210
-> ms port : 3601
-> OS libs : C:usrsapJ2EJC00j2eeos_libs
-> Admin URL :
-> run mode : NORMAL
-> run action : NONE
-> enabled : yes
**********************************************************************
[Thr 1588] Mon Feb 14 20:49:56 2005
[Thr 1588] *** ERROR => Can't attach to administration shared memory (rc=3) [jcmonxx.c 219]
std_bootstrap_ID4250850.out:
--------------------------------------------------------------------------------
stdout/stderr redirect
--------------------------------------------------------------------------------
node name : server0 bootstrap
pid : 3148
system name : J2E
system nr. : 00
started at : Mon Feb 14 20:32:55 2005
Error occurred during initialization of VM
Could not reserve enough space for object heap
I managed to solve the problem. Many helpers indicated that memory problems could be the issue, and that proved to be the case - even though perhaps not as expected.
I decreased Max Heap size from 1024 MB to 512 MB as I mentioned in my last posting and I now also changed one of the parameters from -Xms1024m to -Xms512m.
Classic: It works, but I don't know why. If anyone has an explanation for me, I would appreciate it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That would make sense. Decreasing the Max Heap Size (-Xmx) below the Initial Heap Size (-Xms) would result in having a initial heap being set to the -Xms setting (in this case 1024m) and just never growing beyond that initial size sicne the Maximum size (-Xmx512m) is lower but is only used when checking if growth is allowable.
Did your system have sufficient physical RAM to support a heap size of 1GB? It seems that you should be able to start up under Windows with the originial settings if you have sufficient resources.
This worked for me as well, setting both heap memory to 512MB. One other time, my virtual memory setting was too low and I re-seted the low virtual memory same as the high to 4000MB and it fixed this problem. Any how if anyone with new PCs with Dual Core CPU and 4GB RAM has seen the same issue then please post your result.
I used the config tool (C:\usr\sap\J2E\JC00\j2ee\configtool\configtool.bat) to decrease the heap size to 512MB for the server (both under tab General and tab Bootstrap).
Now the jcontrol.exe process doesn't get marked "stopped". Now it has status "Some processes running".
If I check the process table I can see that the dispatcher and SDM is running, but server0 has stopped with exitcode -2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Lars,
did you make any changes to the JVM memory settings? Have a look at SAP Note 709140 and related note 716604 to make sure the JVM settings of the bootstrap process are correct.
Hope that helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No I haven't made any such changes.
When I tried to solve the problem yesterday I read the notes 709140 and 716604, but the numbers seems OK. I should have mentioned that in my original posting.
From my interpretation of note 709140, I shouldn't even need to mess with the memory size for the bootstrap for new installations ("The default values set by the java virtual machines are sufficient. For some older installations, it may be necessary to set memory parameters for the bootstrap processes (please see platform specific notes)").
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.