jstart never start in NetWeaver CE 7.1

[former_member188321]

Hello Members,

I installed NW CE 7.1, but had nwadmin was not working so I re-installed it.

Now, when I start sapmmc, then jstart.EXE tries to start but stops after 1 minute. When I check the developer trace, end of it says:

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

F Process collector started with pid 5032

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

F [Thr 5756] *** LOG => Process collector started (pid 5032).

F [Thr 5756] *** LOG => Process collector stopping (pid 5032).

F

F [Thr 5296] Sun Nov 02 12:39:30 2008

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

F

F [Thr 5756] Sun Nov 02 12:39:30 2008

F [Thr 5756] *** LOG => Process collector stopped (pid 5032).

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

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

F [Thr 5756] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).

F [Thr 5756] *** LOG => exiting (exitcode 22002, retcode 1).

Could you please help me to resolve this and get it working?

Thanks & Regards,

Daman

[Former Member]

HI ,

Please check below SAP message and increase server count to get it fixed.

1706936 - messages fails with error java.lang.RuntimeException Bean SMPP_CALL_JAVA_RUNTIME3 not foun...

Regards,

Prabhat Mishra

[Former Member]

Otis Jinks, thanks. Your tip regarding maxdb log issue helped me.

[Former Member]

I had the same problem. But it was because the MAXDB log was full. Solution is to install NW-711SP4\MAXDB77INT\DATA_UNITS\MAXDB_WINDOWS_I386\SETUPS\DBM76.exe (MaxDB Database Manager). Then use this GUI to backup the current log and turn on the Auto Log feature. Finally, restart the MAXDB service.

[tbroek]

Hi Daman

Great

-I could start the DB manually by "sapdb\<SID>\db\pgm\dbmstart.exe -d <SID>"

=> c:\sapdb\CE1\db\pgm\dbmstart.exe -d CE1

That did the trick. This resolved my Jstart.exe issue.

Thanks!

Twan

[former_member188321]

-I could start the DB manually by "sapdb\<SID>\db\pgm\dbmstart.exe -d <SID>"

-I tried uninstalling and installing loopback adapter too, but no help

Adding Full Dev. trace:

-

---

trc file: "C:\usr\sap\CE1\J00\work\dev_jstart.5736", trc level: 1, release: "711"

-

---

-

---

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

-

---

sysno 00

sid CE1

systemid 560 (PC with Windows NT)

relno 7110

patchlevel 0

patchno 10

intno 20020600

make multithreaded, Unicode, optimized

profile C:\usr\sap\CE1\SYS\profile\CE1_J00_<machineName>

pid 5736

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS All, egi

*

Sun Nov 02 12:39:18 2008

*

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

*

arguments :

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

arg[ 1] : pf=C:\usr\sap\CE1\SYS\profile\CE1_J00_<machineName>

F

F Sun Nov 02 12:39:18 2008

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

F Java SDK properties (C:\usr\sap\CE1\J00\work\jstart.jvm)

F root directory : C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024/sapjvm_5

F vendor : SAP AG

F version : 1.5.0_14

F cpu : x86

F java vm type : server

F jvm library name : jvm.dll

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

F executable path : C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\bin

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

F SAP extensions : available

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

I [Thr 5756] MtxInit: 30002 0 2

-

---

trc file: "C:\usr\sap\CE1\J00\work\dev_jstart", trc level: 1, release: "711"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS All, egi

*

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

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

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

F Java process [deployment] properties:

F section name : deployment

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

F node name : Deploy_offline

F home directory : C:\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 5756] *** LOG => Instance state is "Deploying offline components" (STARTING @ 0, INACTIVE).

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

F

F Sun Nov 02 12:39:19 2008

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

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

F arg[ 1] = -nodeId=0

F arg[ 2] = pf=C:\usr\sap\CE1\SYS\profile\CE1_J00_<machineName>

F arg[ 3] = -hostvm

F arg[ 4] = -nodeName=deployment

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

F arg[ 6] = -jvmFile=C:\usr\sap\CE1\J00\work\jstart.jvm

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

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

F env : JStart/ReserveSize=0x60000000

F exePath : PATH=C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\bin;C:\usr\sap\CE1\SYS\exe\uc\NTI386;C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\PROGRA~1\SECUDE;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Java\jre1.6.0_03\bin;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Hewlett-Packard\IAM\bin

F libPath : PATH=C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\jre\bin\server;C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\jre\bin;C:\usr\sap\CE1\J00\j2ee\os_libs;C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\bin;C:\usr\sap\CE1\SYS\exe\uc\NTI386;C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\PROGRA~1\SECUDE;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Java\jre1.6.0_03\bin;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Hewlett-Packard\IAM\bin

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

F stderr : C:\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 5952

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

F [Thr 5756] *** LOG => Process deployment started (pid 5952).

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

F

F [Thr 5756] Sun Nov 02 12:39:20 2008

F [Thr 5756] *** LOG => Process deployment stopping (pid 5952).

F

F [Thr 4392] Sun Nov 02 12:39:20 2008

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

F [Thr 5756] *** LOG => Process deployment stopped (pid 5952).

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

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

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

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

F Java process [bootstrap] properties:

F section name : bootstrap

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

F node name : Instance_bootstrap

F home directory : C:\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 5756] *** LOG => Instance state is "Synchronizing binaries" (STARTING @ 0, INACTIVE).

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

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

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

F arg[ 1] = -nodeId=0

F arg[ 2] = pf=C:\usr\sap\CE1\SYS\profile\CE1_J00_<machineName>

F arg[ 3] = -hostvm

F arg[ 4] = -nodeName=bootstrap

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

F arg[ 6] = -jvmFile=C:\usr\sap\CE1\J00\work\jstart.jvm

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

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

F env : JStart/ReserveSize=0x60000000

F exePath : PATH=C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\bin;C:\usr\sap\CE1\SYS\exe\uc\NTI386;C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\PROGRA~1\SECUDE;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Java\jre1.6.0_03\bin;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Hewlett-Packard\IAM\bin

F libPath : PATH=C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\jre\bin\server;C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\jre\bin;C:\usr\sap\CE1\J00\j2ee\os_libs;C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\bin;C:\usr\sap\CE1\SYS\exe\uc\NTI386;C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\PROGRA~1\SECUDE;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Java\jre1.6.0_03\bin;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Hewlett-Packard\IAM\bin

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

F stderr : C:\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 3724

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

F [Thr 5756] *** LOG => Process bootstrap started (pid 3724).

F

F [Thr 5756] Sun Nov 02 12:39:23 2008

F [Thr 5756] *** LOG => Process bootstrap stopping (pid 3724).

F

F [Thr 5324] Sun Nov 02 12:39:23 2008

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

F [Thr 5756] *** LOG => Process bootstrap stopped (pid 3724).

F [Thr 5756] *** WARNING => Node bootstrap failed: result 1, exit code 503. [sfxxnode.hpp 1005]

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

F Java process [collector] properties:

F section name : collector

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

F node name : collector

F home directory : C:\usr\sap\CE1\J00/j2ee

F shutdown timeout : 136000 ms

F exit timeout : 7000 ms

F debuggable : false

F debugger active : false

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

F

F Sun Nov 02 12:39:24 2008

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

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

F arg[ 1] = -nodeId=1000

F arg[ 2] = pf=C:\usr\sap\CE1\SYS\profile\CE1_J00_<machineName>

F arg[ 3] = -DSAPINFO=CE1_00_collector

F arg[ 4] = -hostvm

F arg[ 5] = -nodeName=collector

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

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

F arg[ 8] = -traceFile=C:\usr\sap\CE1\J00\work\dev_collector

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

F arg[10] = -clusterId=bootstrap

F arg[11] = -exitcode

F arg[12] = 503

F env : JStart/ReserveSize=0x60000000

F exePath : PATH=C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\bin;C:\usr\sap\CE1\SYS\exe\uc\NTI386;C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\PROGRA~1\SECUDE;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Java\jre1.6.0_03\bin;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Hewlett-Packard\IAM\bin

F libPath : PATH=C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\jre\bin\server;C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\jre\bin;C:\usr\sap\CE1\J00\j2ee\os_libs;C:\usr\sap\CE1\SYS\exe\jvm\NTI386\sapjvm_5.1.024\sapjvm_5\bin;C:\usr\sap\CE1\SYS\exe\uc\NTI386;C:\sapdb\programs\bin;C:\sapdb\programs\pgm;C:\PROGRA~1\SECUDE;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Java\jre1.6.0_03\bin;C:\Program Files\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Hewlett-Packard\IAM\bin

F stdout : C:\usr\sap\CE1\J00\work\std_collector.out

F stderr : C:\usr\sap\CE1\J00\work\std_collector.out

F console : no

F debugger: no

F nice : yes

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

F Process collector started with pid 5032

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

F [Thr 5756] *** LOG => Process collector started (pid 5032).

F [Thr 5756] *** LOG => Process collector stopping (pid 5032).

F

F [Thr 5296] Sun Nov 02 12:39:30 2008

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

F

F [Thr 5756] Sun Nov 02 12:39:30 2008

F [Thr 5756] *** LOG => Process collector stopped (pid 5032).

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

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

F [Thr 5756] *** LOG => Instance state is "Some processes failed" (STOPPED @ 0, INACTIVE).

F [Thr 5756] *** LOG => exiting (exitcode 22002, retcode 1).

Regards,

Daman

[former_member188321]

Hi,

Also, I looked at /usr/sap/<SID>/J<XX>/j2ee/cluster/server<X>/log/defaultTrace_.trc* file.

I found some entries like:

Warnings:

The Galaxy_Content_Archive container reports that doesn't support parallel operations, which slows down the deploy, update and remove operations with applications.

Solution: Please contact the container holder to fix these warnings.#

#2.0 #2008 11 02 11:16:23:225#+0530#Error#com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa#

#BC-ESI-WS-JAV#tc_esiesp_{srv#02004C4F4F5000120000000400001200#6447350000000780##com.sap.esi.esp.service.server.query.discovery.DestinationsHelperImplSoa####3DF9B940A8A111DDA72D02004C4F4F50#3df9b940a8a111dda72d02004c4f4f50#3df9b940a8a111dda72d02004c4f4f50#0#Service Runner [tc}esi_espsrv]#Plain##

the destination application : sap.com/tc_esiesp_destinationwsar is not available and cannot perform migration#

#2.0 #2008 11 02 11:16:26:408#+0530#Error#com.sap.engine.services.ejb3.runtime#

#BC-JAS-EJB#ejb#02004C4F4F5000130000000000001200#6447350000000767##com.sap.engine.services.ejb3.runtime#Guest#0##3DF9B940A8A111DDA72D02004C4F4F50#3df9b940a8a111dda72d02004c4f4f50#3df9b940a8a111dda72d02004c4f4f50#0#Application [17]#Java##

Error occurs while the EJB Object Factory trying to resolve JNDI reference Reference Class Name:

Type: clientAppName

Content: sap.com/tc_esiesp_wsrmapp

Type: interfaceType

Content: local

Type: ejb-link

Content: ReliableMessagingListener

Type: jndi-name

Content: ReliableMessagingListener

Type: local-home

Content: com.sap.engine.services.wsrm.ms.listeners.ReliableMessagingListenerHome

Type: local

Content: com.sap.engine.services.wsrm.ms.listeners.ReliableMessagingListener

com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/tc_esiesp_wsrmapp; nested exception is: java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5106] The application [sap.com/tc_esiesp_wsrmapp] will not be started, because of the server state is [STARTING].

at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.startApp(DefaultContainerRepository.java:315)

at com.sap.engine.services.ejb3.runtime.impl.DefaultContainerRepository.getEnterpriseBeanContainer(DefaultContainerRepository.java:106)

at com.sap.engine.services.ejb3.runtime.impl.DefaultRemoteObjectFactory.resolveReference(DefaultRemoteObjectFactory.java:55)

[EXCEPTION]

#1#com.sap.engine.services.ejb3.runtime.impl.refmatcher.EJBResolvingException: Cannot start applicationsap.com/tc_esiesp_wsrmapp; nested exception is: java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5106] The application [sap.com/tc_esiesp_wsrmapp] will not be started, because of the server state is [STARTING].

java.rmi.RemoteException: [ERROR CODE DPL.DS.6125] Error occurred while starting application locally and wait.; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5106] The application [sap.com/tc_esiesp_wsrmapp] will not be started, because of the server state is [STARTING].

etc.