Sapmmc - jstart.exe keeps restarting, switching between green and yellow

Question

Hi Friends,
I installed the SAP core server ( as part of SAP convergent charging) , but jstart.exe and dispatcher-1 process in sapmmc are noticed keep switching between yellow and green. when the jstart.exe turns green (all process running) , dispatcher-1 turns yellow (waiting to start) and when dispatcher-1 turns green (restart-yes) , jstart.exe turns yellow (some processes running). Only for a small duration , they both remain green (may be during transition).
Trace File is as below: Iam not sure as what is missing here to be installed, as it is complaining about JEE directory in
C:\usr\sap\C06\CCD09\j2ee\cluster\bin, which is not present., which was never installed as part of the installation.
trc file: "dev_jstart.new", trc level: 1, release: "711"
sysno      09
sid        C06
systemid   562 (PC with Windows NT)
relno      7110
patchlevel 0
patchno    92
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    C:\usr\sap\C06\SYS\profile\C06_CCD09_W2K8-Sap-01
pid        3596
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      All, egi
Wed Oct 26 04:53:47 2011
trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
  arg[ 0] : C:\usr\sap\C06\CCD09\exe\jstart.EXE
  arg[ 1] : pf=C:\usr\sap\C06\SYS\profile\C06_CCD09_W2K8-Sap-01
trc file: "C:\usr\sap\C06\CCD09\work\dev_jstart", trc level: 1, release: "711"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      All, egi
F 
F [Thr 3600] Wed Oct 26 04:53:47 2011
F  [Thr 3600] *** ERROR => SfCheckJeeVersion: Cannot find JEE binary directory C:\usr\sap\C06\CCD09\j2ee\cluster\bin. [sfxxmain.cpp 848]
trc file: "C:\usr\sap\C06\CCD09\work\dev_jstart", trc level: 1, release: "711"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      All, egi
F  [Thr 3600] *** ERROR => SfCheckJeeVersion: Cannot find JEE application directory C:\usr\sap\C06\CCD09\j2ee\cluster\apps. [sfxxmain.cpp 857]
F  ********************************************************************************
F  Java environment properties (C:\usr\sap\C06\CCD09\work\jstart.jvm)
F    root directory    : C:\usr\sap\C06\CCD09\exe\sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_24
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.027 1.6-b07
F    jvm library name  : jvm.dll
F    library path      : C:\usr\sap\C06\CCD09\exe\sapjvm_6\jre\bin\server;C:\usr\sap\C06\CCD09\exe\sapjvm_6\jre\bin
F    executable path   : C:\usr\sap\C06\CCD09\exe\sapjvm_6\bin
F  ********************************************************************************
F    SAP extensions    : available
F  ********************************************************************************
I  [Thr 3600] MtxInit: 30002 0 2
dispatcher trace
trc file: "C:\usr\sap\C06\CCD09\work\dev_dispatcher-1", trc level: 1, release: "711"
sysno      09
sid        C06
systemid   562 (PC with Windows NT)
relno      7110
patchlevel 0
patchno    92
intno      20020600
make       multithreaded, Unicode, 64 bit, optimized
profile    C:\usr\sap\C06\SYS\profile\C06_CCD09_W2K8-Sap-01
pid        428
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      All, egi
Wed Oct 26 06:22:16 2011
trace logging activated, max size = 52428800 bytes, 2 versions
arguments :
  arg[ 0] : C:\usr\sap\C06\CCD09\exe\jstart.EXE
  arg[ 1] : -appTrc
  arg[ 2] : -nodeId=0
  arg[ 3] : pf=C:\usr\sap\C06\SYS\profile\C06_CCD09_W2K8-Sap-01
  arg[ 4] : -hostvm
  arg[ 5] : -nodeName=dispatcher-1
  arg[ 6] : -file=C:\usr\sap\C06\CCD09\config\jstart.config
  arg[ 7] : -jvmFile=C:\usr\sap\C06\CCD09\work\jstart.jvm
  arg[ 8] : -traceFile=C:\usr\sap\C06\CCD09\work\dev_dispatcher-1
  arg[ 9] : -javaOutFile=C:\usr\sap\C06\CCD09\work\jvm_dispatcher-1.out
F 
F Wed Oct 26 06:22:16 2011
F  ********************************************************************************
F  Java environment properties
F    root directory    : C:\usr\sap\C06\CCD09\exe\sapjvm_6
F    vendor            : SAP AG
F    version           : 1.6.0_24
F    cpu               : amd64
F    java vm type      : server
F    java vm version   : 6.1.027 1.6-b07
F    jvm library name  : jvm.dll
F    library path      : C:\usr\sap\C06\CCD09\exe\sapjvm_6\jre\bin\server;C:\usr\sap\C06\CCD09\exe\sapjvm_6\jre\bin
F    executable path   : C:\usr\sap\C06\CCD09\exe\sapjvm_6\bin
F    SAP extensions    : available
F  ********************************************************************************
I  [Thr 3828] MtxInit: 10000 0 2
M  [Thr 3828] NiInit3: NI already initialized; param 'maxHandles' ignored (init=2;par=202;cur=2048)
M  [Thr 3828] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
M  [Thr 3828] CCMS: Initalized shared memory of size 60000000 for monitoring segment.
M  [Thr 3828] CCMS: Checking Downtime Configuration of Monitoring Segment.
M 
M [Thr 3828] Wed Oct 26 06:22:17 2011
M  [Thr 3828] CCMS: AlMsUpload called by wp 1004.
M  [Thr 3828] CCMS: AlMsUpload failed for C:\usr\sap\C06\CCD09\log\ALMTTREE.DAT.
M  [Thr 3828] CCMS: CCMS Monitoring Initialization finished, rc=0.
F 
Please help.
Thanks.
Edited by: Zain Ahmed on Oct 26, 2011 9:07 PM

Answer 1

HI,
Import the SAP profiles in SAP transaction RZ10: Utilities - Import profiles - of Active Server
OR
Check what messages do you have in jvm_server0.out, dev_server0.out and bootstrap traces,
also have a look at the note 142100.
The first problem is that in the SCS instance there are no running enqueue server as its starting line have no line break at the end in the start profile. Without this NT cannot parse the line. After adding the line break the enqueue server could start.
The second problem is that in the global dispatcher configuration for the LockingManager the en.port was set to 3201 instead of 3200 (which is correct as the SCS instance has the intance number 00).
After correcting these problems the J2EE engine could be started fine.
see similar threads
Dispatcher - Running but Dialog Queue info unavailable
/thread/96588 [original link is broken]
logon710
Message server not starting
Thanks
Swarup