Exitcode -1501 trying to start java server process

[Former Member]

Hello!

I have installed SAP NetWeaver Composition Environment 7.1 SR5 Evalution SDN Version on a windows xp machine.

Included is the J2EE Application Server and the MaxDB.

I have done a standard installation (no adjustments)

When I try to start the Application Server with the management console it does not work.

The DB is running and I can log on via management console. I can connect to the database with the config tool.

Tha app server starts but in status it says "Some processes running [Safe Mode]" (yellow symbol)

With in the management console I see under "AS Java Process Table" that the process server0 has not started.

The trace file states:

J Wed Jul 22 15:21:50 2009

J [GC [ParNew: 9808K->2872K(10944K), 0.0070266 secs] 12456K->5521K(127488K), 0.0071551 secs]

F

F [Thr 4016] Wed Jul 22 15:21:51 2009

F [Thr 4016] *** LOG => SfCJavaVm: exit hook is called. (rc = -1501)

F [Thr 4016] *** LOG => exiting (exitcode -1501, retcode 2).

M [Thr 4016] CCMS: CCMS Monitoring Cleanup finished successfully.

Afterwards the server stops.

Does anyone have an idea what exitcode -1501 means?? I haven't found anything in these forums.

I checked the other logs but there were no errors.

Thanks in advance,

Jens

[desiree_matas]

Hi Jens,

At it is quite difficult to analyze the issue in this way, maybe you could open a message at the SAPNet R/3 Frontend (formerly called u201COSSu201D), under component BC-JAS-SF

Regards,

Désiré

[Former Member]

Hi Jen,

did you already solve this problem?

[Former Member]

sorry, no solution yet...

[Former Member]

Hi Jens,

I have exactly the same problem starting 7.1 CE EHP1 with Oracle 10.2.0.4. The tail of my developer trace file looks like this:

F [Thr 3532] Wed Dec 16 11:33:32 2009

F [Thr 3532] *** LOG => Signal 13 SIGCHLD.

F [Thr 4464] *** LOG => Process server0 stopped (pid 5960).

F [Thr 4464] *** WARNING => Node server0 failed: result 2, exit code -1501. [sfxxnode.hpp 1005]

F ********************************************************************************

F Java process [collector] properties:

F section name : collector

F config file : S:\usr\sap\ERT\J00\exe\startup.properties

F node name : collector

F home directory : S:\usr\sap\ERT\J00/j2ee

F shutdown timeout : 136000 ms

F exit timeout : 7000 ms

F debuggable : false

F debugger active : false

F ********************************************************************************

F ********************************************************************************

F Starting process: S:\usr\sap\ERT\J00\exe\jstart.EXE

F arg[ 1] = -nodeId=1002

F arg[ 2] = pf=S:\usr\sap\ERT\SYS\profile\ERT_J00_gbebpmesmiis

F arg[ 3] = -DSAPINFO=ERT_00_collector

F arg[ 4] = -hostvm

F arg[ 5] = -nodeName=collector

F arg[ 6] = -file=S:\usr\sap\ERT\J00\exe\startup.properties

F arg[ 7] = -jvmFile=S:\usr\sap\ERT\J00\work\jstart.jvm

F arg[ 8] = -traceFile=S:\usr\sap\ERT\J00\work\dev_collector

F arg[ 9] = -javaOutFile=S:\usr\sap\ERT\J00\work\jvm_collector.out

F arg[10] = -clusterId=ID8222850

F arg[11] = -exitcode

F arg[12] = -1501

F exePath : PATH=S:\usr\sap\ERT\J00\exe\sapjvm_5\bin;S:\usr\sap\ERT\J00\exe;D:\oracle\ETH\102\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F libPath : PATH=S:\usr\sap\ERT\J00\exe\sapjvm_5\jre\bin\server;S:\usr\sap\ERT\J00\exe\sapjvm_5\jre\bin;S:\usr\sap\ERT\J00\j2ee\os_libs;S:\usr\sap\ERT\J00\exe\sapjvm_5\bin;S:\usr\sap\ERT\J00\exe;D:\oracle\ETH\102\bin;C:\Program Files\HP\NCU;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F stdout : S:\usr\sap\ERT\J00\work\std_collector.out

F stderr : S:\usr\sap\ERT\J00\work\std_collector.out

F console : no

F debugger: no

F nice : no

F ********************************************************************************

F Process collector started with pid 1400

F ********************************************************************************

F [Thr 4464] *** LOG => Process collector started (pid 1400).

F

F [Thr 4464] Wed Dec 16 11:33:48 2009

F [Thr 4464] *** LOG => Process collector stopping (pid 1400).

F

F [Thr 4168] Wed Dec 16 11:33:48 2009

F [Thr 4168] *** LOG => Signal 13 SIGCHLD.

F [Thr 4464] *** LOG => Process collector stopped (pid 1400).

F [Thr 4464] *** LOG => Removing enque locks for ID 8222850.

F [Thr 4464] *** LOG => Instance state is "Some processes running" (RUNNING @ 0, INACTIVE).

The only obvious error in the trace file is on the 4th line down, which states:

F [Thr 4464] *** WARNING => Node server0 failed: result 2, exit code -1501. [sfxxnode.hpp 1005]

I've searched everywhere I can for an answer, but cannot find anything.

Did you get this fixed?

Kind regards,

Arwel Owen

Princes Ltd

Liverpool, UK.

[Former Member]

Hello,

Please stop the instance completely. I mean both CI and SCS instance. Make sure there are no processes running under Task Manager.

After that start ur SCS instance and then try starting CI. Since the problem is with starting Confugiration manager, it seems server nodes are not able to connect with the SCS instance.

Thanks & Regards,

Denish