Detail: ICM running but no server with HTTP connected

[Former Member]

Hi,

I installed SAP NetWeaver Composition Environment 7.1 SR5 - Trial Version from https://www.sdn.sap.com/irj/scn/nw-ce-downloads.

When I want going Portal I set address as:

http://localhost:50000/

or

http://ih82bl84f1:50000/

in result I get the same error:

503 Service not available

----

---

Error: -6

Version: 7010

Component: ICM Java

Date/Time: Thu Feb 05 06:13:47 2009

Module: http_j2ee2.c

Line: 764

Server: ih82bl84f1_CE1_00

Error Tag: {-}

Detail: ICM running but no server with HTTP connected

What can I do to use the Portal?

I don't have ABAP stack, only JAVA.

In sapmmc Process jstart.EXE has a status Some processes running

but proceses:

msg_server.EXE

enserver.EXE

gwrd.EXE

are Running

Thanks,

Bogdan

[younghwan_kim · Accepted solution]

It means server doesn't work anyway,so ICM can't connect your request to server.

I should you just have to wait enough until all processes should be running, NOT SOME PROCESS IS RUNNING.

[Former Member · Accepted solution]

OK, but how long I must wait?

max time?

I'd like add that all system stand on Virtual PC (at my laptop - with 2GB RAM)

Thanks.

Edited by: Bogdan Radziejowski on Mar 13, 2009 1:51 AM

[younghwan_kim · Accepted solution]

It depends on your PC spec. It takes about 10 to 20 minutes, I think.

Anyway, in MMC, expand all tress, and you can see "As Java Process Table".

There are three processes, SDM, dispatcher, and server0.

The status of all three processes has changed to "running", then you are ready to work.

[Former Member · Accepted solution]

unfortunately jstart.EXE = Some processes running

.... In sapmmc Process jstart.EXE has a status Some processes running

but proceses:

msg_server.EXE

enserver.EXE

gwrd.EXE

are Running....

[hofmann · Accepted solution]

Hi,

"Some processes running" means that the AS Java is still in the startup phase. You'll normally have to wait for until all processes are started. It help if you add more RAM to servernode 0 (> 1,5 gb).

I'm not familiar with the license issues, but with the demo version for NetWeaver 7 there is also the issue that you have to apply the license within 30 minutes. If not, the java instance will get shut down. Can you access the NWA (/nwa) and check if the license is applied?

br,

Tobias

[Former Member · Accepted solution]

Hi,

Thank you for your suggestion - unfortunately, I have still the same problem.

I leave my laptop for all night (about 10h) and gets two massage:

1.

... In sapmmc Process jstart.EXE has a status Processes running

but proceses:

msg_server.EXE

enserver.EXE

gwrd.EXE

are Running....

2. and from win XP that memory RAM is overflow. (virtual machine 1,46GB RAM)

br,

Bogdan

[Former Member · Accepted solution]

I think that I don't need licence, because I use trail version.

[hofmann · Accepted solution]

Hi,

check the 2. point, Memory RAM overflow. Try to add as much RAM to the VM as possible. What's the recommendaton from SAP for this Trial?

In the startup phase, NW loads all servlets, portlets, SAP stuff. This needs quite a lot of memory. What's happening on your hard drive? Is it swapping a lot? If so, add more RAM to the VM + servernode.

br,

Tobias

[Former Member · Accepted solution]

Thank you Tobias,

I've used before Virual PC - and I can't add RAM in this app. I have 3GB RAM on my local laptop, when I used Virual PC a max RAM I can fix 1,5GB. More I can't, because VPC can't started.

For me better is VMware - I set 2048MB RAM and then everything is OK.

all process running :).

br,

Bogdan

[Former Member · Accepted solution]

I am also facing the same problem

In dev_server0 log file it has exit code -21001 and ret code 2

I have 3 GB ram installed in my system........

In SAP MMC AS Java Process Table it has 3 processes,they are as follows.

debugproxy - disabled

icm - running

server0 - stopped

jstart.exe status is "Some processes are running"

please help me.....

Reply would be appreciated

[Former Member]

Hi,

Can you post the dev_jstart and also latest log files in the work folder. can you try with using IP address instead of the hostname

Mahesh

[Former Member]

---

trc file: "dev_jstart.2360", trc level: 1, release: "710"

-

---

-

---

trc file: "dev_jstart.new", trc level: 1, release: "710"

-

---

sysno 00

sid CE1

systemid 560 (PC with Windows NT)

relno 7100

patchlevel 0

patchno 88

intno 20020600

make multithreaded, Unicode, optimized

profile E:\usr\sap\CE1\SYS\profile\CE1_J00_ih82bl84f1

pid 2360

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS All, egi

*

Sun Mar 08 16:36:39 2009

*

• trace logging activated, max size = 52428800 bytes, 2 versions

*

arguments :

arg[ 0] : E:\usr\sap\CE1\SYS\exe\uc\NTI386\jstart.EXE

arg[ 1] : pf=E:\usr\sap\CE1\SYS\profile\CE1_J00_ih82bl84f1

-

---

trc file: "dev_jstart", trc level: 1, release: "710"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS All, egi

*

F

F [Thr 2352] Sun Mar 08 16:36:39 2009

F [Thr 2352] *** ERROR => SfCheckJeeVersion: Cannot find JEE application directory E:\usr\sap\CE1\J00\j2ee\cluster\apps. [sfxxmain.cpp 863]

F

F Sun Mar 08 16:36:47 2009

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

F Java SDK properties (E:\usr\sap\CE1\J00\work\jstart.jdk)

F root directory : E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017/sapjvm_5

F vendor : SAP AG

F version : 1.5.0_13

F cpu : x86

F java vm type : server

F jvm library name : jvm.dll

F library path : E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\jre\bin\server;E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\jre\bin

F executable path : E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\bin

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

F SAP extensions : available

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

I [Thr 2352] MtxInit: 30002 0 2

-

---

trc file: "dev_jstart", trc level: 1, release: "710"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS All, egi

*

F [Thr 2352] *** LOG => connected to Enqueue Server.

F [Thr 2352] *** LOG => connected to Message Server.

F [Thr 2352] *** LOG => Starting run level 1.

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

F Java process [deployment] properties:

F section name : deployment

F config file : E:\usr\sap\CE1\SYS\exe\uc\NTI386\startup.properties

F node name : Deploy_offline

F home directory : E:\usr\sap\CE1\J00\j2ee\cluster

F shutdown timeout : 136000 ms

F exit timeout : 7000 ms

F debuggable : false

F debugger active : false

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

F [Thr 2352] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).

F [Thr 2352] *** LOG => Starting nodes: runlevel 1.

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

F Starting process: E:\usr\sap\CE1\SYS\exe\uc\NTI386\jstart.EXE

F arg[ 1] = -nodeId=0

F arg[ 2] = pf=E:\usr\sap\CE1\SYS\profile\CE1_J00_ih82bl84f1

F arg[ 3] = -hostvm

F arg[ 4] = -nodeName=deployment

F arg[ 5] = -file=E:\usr\sap\CE1\SYS\exe\uc\NTI386\startup.properties

F arg[ 6] = -jdkFile=E:\usr\sap\CE1\J00\work\jstart.jdk

F arg[ 7] = -traceFile=E:\usr\sap\CE1\J00\work\dev_deployment

F arg[ 8] = -javaOutFile=E:\usr\sap\CE1\J00\work\jvm_deployment.out

F env : JStart/ReserveSize=0x60000000

F exePath : PATH=E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\bin;E:\sapdb\programs\bin;E:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F libPath : PATH=E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\jre\bin\server;E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\jre\bin;E:\usr\sap\CE1\J00\j2ee\os_libs;E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\bin;E:\sapdb\programs\bin;E:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F stdout : E:\usr\sap\CE1\J00\work\std_deployment.out

F stderr : E:\usr\sap\CE1\J00\work\std_deployment.out

F console : no

F debugger: no

F nice : yes

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

F Process Deploy_offline started with pid 3752

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

F [Thr 2352] *** LOG => Process deployment started (pid 3752).

F

F [Thr 2352] Sun Mar 08 16:37:19 2009

F [Thr 2352] *** LOG => Process deployment stopping (pid 3752).

F

F [Thr 3760] Sun Mar 08 16:37:19 2009

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

F [Thr 2352] *** LOG => Process deployment stopped (pid 3752).

F [Thr 2352] *** LOG => Instance state is "Deploying offline components" (STOPPING @ 0, INACTIVE).

F [Thr 2352] *** LOG => Run level 1 completed.

F [Thr 2352] *** LOG => Starting run level 2.

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

F Java process [bootstrap] properties:

F section name : bootstrap

F config file : E:\usr\sap\CE1\SYS\exe\uc\NTI386\startup.properties

F node name : Instance_bootstrap

F home directory : E:\usr\sap\CE1\J00\j2ee\cluster

F shutdown timeout : 136000 ms

F exit timeout : 7000 ms

F debuggable : false

F debugger active : false

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

F [Thr 2352] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).

F [Thr 2352] *** LOG => Starting nodes: runlevel 2.

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

F Starting process: E:\usr\sap\CE1\SYS\exe\uc\NTI386\jstart.EXE

F arg[ 1] = -nodeId=0

F arg[ 2] = pf=E:\usr\sap\CE1\SYS\profile\CE1_J00_ih82bl84f1

F arg[ 3] = -hostvm

F arg[ 4] = -nodeName=bootstrap

F arg[ 5] = -file=E:\usr\sap\CE1\SYS\exe\uc\NTI386\startup.properties

F arg[ 6] = -jdkFile=E:\usr\sap\CE1\J00\work\jstart.jdk

F arg[ 7] = -traceFile=E:\usr\sap\CE1\J00\work\dev_bootstrap

F arg[ 8] = -javaOutFile=E:\usr\sap\CE1\J00\work\jvm_bootstrap.out

F env : JStart/ReserveSize=0x60000000

F exePath : PATH=E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\bin;E:\sapdb\programs\bin;E:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F libPath : PATH=E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\jre\bin\server;E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\jre\bin;E:\usr\sap\CE1\J00\j2ee\os_libs;E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\bin;E:\sapdb\programs\bin;E:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F stdout : E:\usr\sap\CE1\J00\work\std_bootstrap.out

F stderr : E:\usr\sap\CE1\J00\work\std_bootstrap.out

F console : no

F debugger: no

F nice : yes

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

F Process Instance_bootstrap started with pid 908

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

F [Thr 2352] *** LOG => Process bootstrap started (pid 908).

F

F [Thr 2352] Sun Mar 08 16:37:32 2009

F [Thr 2352] *** LOG => Process bootstrap running (pid 908).

F [Thr 2352] *** LOG => Instance state is "Synchronizing binaries" (RUNNING @ 0, INACTIVE).

F

F [Thr 2352] Sun Mar 08 16:37:44 2009

F [Thr 2352] *** LOG => Process bootstrap stopping (pid 908).

F

F [Thr 492] Sun Mar 08 16:37:44 2009

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

F [Thr 2352] *** LOG => Process bootstrap stopped (pid 908).

F [Thr 2352] *** LOG => Instance state is "Synchronizing binaries" (STOPPING @ 0, INACTIVE).

F [Thr 2352] *** LOG => Run level 2 completed.

F [Thr 2352] *** LOG => Starting run level 3.

F

F Sun Mar 08 16:37:45 2009

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

F Java process [debugproxy] properties:

F section name : debugproxy

F config file : E:\usr\sap\CE1\SYS\exe\uc\NTI386\dproxy.properties

F node name : Debug_Proxy

F home directory : E:\usr\sap\CE1\J00/j2ee/rdbg.proxy

F shutdown timeout : 136000 ms

F exit timeout : 7000 ms

F debuggable : false

F debugger active : false

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

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

F ICM process [icm] properties:

F section name : icm

F config file : E:\usr\sap\CE1\SYS\exe\uc\NTI386\icm.properties

F node name : ICM

F home directory : E:\usr\sap\CE1\J00\work

F shutdown timeout : 122000 ms

F exit timeout : 7000 ms

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

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

F Java process [server0] properties:

F section name : ID2143550

F config file : E:\usr\sap\CE1\J00\j2ee\cluster\instance.properties

F node name : server0

F home directory : .

F shutdown timeout : 136000 ms

F exit timeout : 7000 ms

F debuggable : true

F debugger active : false

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

F [Thr 2352] *** LOG => Instance state is "Starting the processes" (STARTING @ 0, INACTIVE).

F [Thr 2352] *** LOG => Starting nodes: runlevel 3, phase 0.

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

F Starting process: E:\usr\sap\CE1\SYS\exe\uc\NTI386\icman.EXE

F arg[ 1] = pf=E:\usr\sap\CE1\SYS\profile\CE1_J00_ih82bl84f1

F arg[ 2] = -nodeId=1

F arg[ 3] = -f

F arg[ 4] = E:\usr\sap\CE1\J00\work\dev_icm

F exePath : PATH=E:\sapdb\programs\bin;E:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F libPath : PATH=E:\sapdb\programs\bin;E:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F stdout : E:\usr\sap\CE1\J00\work\std_icm.out

F stderr : E:\usr\sap\CE1\J00\work\std_icm.out

F console : no

F debugger: no

F nice : yes

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

F Process ICM started with pid 1828

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

F [Thr 2352] *** LOG => Process icm started (pid 1828).

F

F [Thr 2352] Sun Mar 08 16:37:46 2009

F [Thr 2352] *** LOG => Process icm running (pid 1828).

F [Thr 2352] *** LOG => Starting nodes: runlevel 3, phase 1.

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

F Starting process: E:\usr\sap\CE1\SYS\exe\uc\NTI386\jstart.EXE

F arg[ 1] = -nodeId=2

F arg[ 2] = pf=E:\usr\sap\CE1\SYS\profile\CE1_J00_ih82bl84f1

F arg[ 3] = -DSAPINFO=CE1_00_server0

F arg[ 4] = -hostvm

F arg[ 5] = -nodeName=ID2143550

F arg[ 6] = -file=E:\usr\sap\CE1\J00\j2ee\cluster\instance.properties

F arg[ 7] = -jdkFile=E:\usr\sap\CE1\J00\work\jstart.jdk

F arg[ 8] = -traceFile=E:\usr\sap\CE1\J00\work\dev_server0

F arg[ 9] = -javaOutFile=E:\usr\sap\CE1\J00\work\jvm_server0.out

F env : JStart/ReserveSize=0x60000000

F exePath : PATH=E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\bin;E:\sapdb\programs\bin;E:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F libPath : PATH=E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\jre\bin\server;E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\jre\bin;E:\usr\sap\CE1\J00\j2ee\os_libs;E:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.017\sapjvm_5\bin;E:\sapdb\programs\bin;E:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

F stdout : E:\usr\sap\CE1\J00\work\std_server0.out

F stderr : E:\usr\sap\CE1\J00\work\std_server0.out

F console : no

F debugger: no

F nice : yes

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

F Process server0 started with pid 1552

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

F [Thr 2352] *** LOG => Process server0 started (pid 1552).

[Former Member]

when I use IP instead hostname effect is the same to before.