J2EE Engine is not comming up.

Dear All,
I was trying to run BSP applications on BW to accomplish this I change WORKGROUP to domain to create FQDN.(NW04 is running on Windows 2003 server). My system is dual stack system.
After restart I can login to the ABAP system but & JAVA Engine is down. I can see the message in MMC "J2ee information unavailable". I go through the trace files below are the some part of traces.
dev_jcontrol
[Thr 520] JControlICheckProcessList: process SDM started (PID:5084)
[Thr 520] Thu Aug 21 04:42:20 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:6108) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
[Thr 520] JControlICheckProcessList: process server0 (pid:2916) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
[Thr 520] JControlICheckProcessList: process SDM (pid:5084) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
dev_dispatcher
[Thr 4560] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4560] JLaunchRequestQueueInit: create pipe listener thread
[Thr 4248] JLaunchRequestFunc: Thread 4248 started as listener thread for np messages.
[Thr 4220] WaitSyncSemThread: Thread 4220 started as semaphore monitor thread.
[Thr 4560] *** ERROR => JLaunchInitAdministration: Can't attach to administration shared memory (rc = 2) [jlnchxx.c    868]
[Thr 4560] *** ERROR => can't initialize JControl Administration [jlnchxx.c    372]
[Thr 4560] JLaunchCloseProgram: good bye (exitcode = 2)
std_server0.out
stdout/stderr redirect
node name   : server0
pid         : 3548
system name : BWT
system nr.  : 10
started at  : Thu Aug 21 04:42:15 2008
Reserved 1610612736 (0x60000000) bytes before loading DLLs.
[Thr 4424] *** ERROR => ShmCreate: Key=68 Inv.Size: req.=73488, alloc.=41168 [shmnt0.c     615]
Critical Error
Can't initialize JControl Administration
-> Unknown error code (rc = 2)
From above I am getting the error is because of Shared memory. My system is of 4 GB & 40 GB of Virtual memory. This problem occurs after changing from WORKGROUP to DOMAIN. I have given all the rights of local administrator to <SID>adm & SAPService<SID> user.
Please help me to resolve this issue.
Thanks & Regards,
Shambo

-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 256M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID106496700
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=bootstrap_ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_bootstrap_ID106496700.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_bootstrap_ID106496700.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_bootstrap_ID106496700
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] Thu Aug 21 04:41:55 2008
[Thr 520] JControlExecuteBootstrap: execute bootstrap process [bootstrap_ID106496750]
[Thr 520] [Node: server0 bootstrap] java home is set by profile parameter
#Java Home: C:\j2sdk1.4.2_12
[Thr 520] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
JStartupIReadSection: read node properties [bootstrap_ID106496750]
-> node name          : server0 bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    : -Djco.jarm=1
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 256M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs
-> main class         : com.sap.engine.offline.OfflineToolStart
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID106496750
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_bootstrap
-> arg[03] = -nodeId=-1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=bootstrap_ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_bootstrap_ID106496750.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_bootstrap_ID106496750.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_bootstrap_ID106496750
-> arg[10] = -mode=BOOTSTRAP
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] Thu Aug 21 04:41:59 2008
[Thr 520] JControlIBuildProcessList: Maximum error count is set to 4
[Thr 5488] JControlRequestFunc: Thread 5488 started as listener thread for np messages.
[Thr 520] [Node: dispatcher] java home is set by profile parameter
#Java Home: C:\j2sdk1.4.2_12
[Thr 520] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
JStartupIReadSection: read node properties [ID106496700]
-> node name          : dispatcher
-> node type          : dispatcher
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.sy
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 545M
-> init heap size     : 545M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\dispatcher
-> class path         : .\bin\boot\boot.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
[Thr 520] [Node: server0] java home is set by profile parameter
#Java Home: C:\j2sdk1.4.2_12
[Thr 520] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
JStartupIReadSection: read node properties [ID106496750]
-> node name          : server0
-> node type          : server
-> node execute       : yes
-> jlaunch parameters :
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    : -Djava.security.policy=./java.policy -Djava.security.egd=file:/dev/urandom -Dorg.omg.CORBA.ORBClass=com.sap.engine.sy
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 1024M
-> init heap size     : 1024M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\server0
-> class path         : .\bin\boot\boot.jar;.\bin\boot\jaas.jar;.\bin\system\bytecode.jar;.
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs
-> main class         : com.sap.engine.boot.Start
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> parameters         :
-> debuggable         : no
-> debug mode         : no
-> debug port         : 51021
-> shutdown timeout   : 120000
[Thr 520] INFO: Invalid property value [Debbugable=yes]
[Thr 520] [Node: SDM] java home is set by profile parameter
#Java Home: C:\j2sdk1.4.2_12
[Thr 520] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
JStartupIReadSection: read node properties [sdm]
-> node name          : SDM
-> node type          : sdm
-> node execute       : yes
-> java path          : C:\j2sdk1.4.2_12
-> java parameters    :
-> java vm version    : 1.4.2_12-b03
-> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
-> java vm type       : server
-> java vm cpu        : x86
-> heap size          : 128M
-> root path          : E:\usr\sap\BWT\DVEBMGS10\SDM\program
-> class path         : E:\usr\sap\BWT\DVEBMGS10\SDM\program\bin\SDM.jar
-> OS libs path       : E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs
-> main class         : SDMInternal
-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
-> framework path     : E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jstartup.jar;E:\usr\sap\BWT\SYS\exe\nuc\NTI386\jvmx.jar
-> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
-> parameters         : server sdmhome=E:\usr\sap\BWT\DVEBMGS10\SDM\program
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120000
[Thr 520] JControlMSConnect: attached to message server (bwtraining/3900)
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
[Thr 4592] JControlMSMessageFunc: Thread 4592 started as listener thread for ms messages.
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_dispatcher.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_dispatcher.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_dispatcher
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process dispatcher started (PID:296)
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_server0.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_server0.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_server0
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process server0 started (PID:5264)
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_sdm.out
-> arg[08] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_sdm.out
-> arg[09] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_sdm
-> arg[10] = -mode=JCONTROL
-> arg[11] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[12] = -DSAPSTART=1
-> arg[13] = -DCONNECT_PORT=1373
-> arg[14] = -DSAPSYSTEM=10
-> arg[15] = -DSAPSYSTEMNAME=BWT
-> arg[16] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[17] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[18] = -DFRFC_FALLBACK=ON
-> arg[19] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process SDM started (PID:2860)
[Thr 520] JControlMSSendLogon: delete SDM logon information (rc=0)
[Thr 520] Thu Aug 21 04:42:04 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:296) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (1)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_dispatcher.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_dispatcher.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_dispatcher
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process dispatcher started (PID:4556)
[Thr 520] JControlICheckProcessList: process server0 (pid:5264) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (1)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process server0 started (PID:5344)
[Thr 520] JControlICheckProcessList: process SDM (pid:2860) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (1)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_sdm.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_sdm.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_sdm
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process SDM started (PID:3900)
[Thr 520] Thu Aug 21 04:42:09 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:4556) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (2)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_dispatcher.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_dispatcher.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_dispatcher
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process dispatcher started (PID:3008)
[Thr 520] JControlICheckProcessList: process server0 (pid:5344) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (2)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process server0 started (PID:5176)
[Thr 520] JControlICheckProcessList: process SDM (pid:3900) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (2)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_sdm.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_sdm.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_sdm
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] Thu Aug 21 04:42:10 2008
[Thr 520] JControlICheckProcessList: process SDM started (PID:2668)
[Thr 520] Thu Aug 21 04:42:15 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:3008) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (3)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_dispatcher
-> arg[03] = -nodeId=0
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496700
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_dispatcher.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_dispatcher.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_dispatcher
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process dispatcher started (PID:6108)
[Thr 520] JControlICheckProcessList: process server0 (pid:5176) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (3)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_server
-> arg[03] = -nodeId=1
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\j2ee\cluster\instance.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=ID106496750
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_server0.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_server0.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_server0
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process server0 started (PID:2916)
[Thr 520] JControlICheckProcessList: process SDM (pid:2668) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (3)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
JControlStartJLaunch: program = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[00] = E:\usr\sap\BWT\DVEBMGS10\exe\jlaunch.exe
-> arg[01] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[02] = -DSAPINFO=BWT_10_sdm
-> arg[03] = -nodeId=2
-> arg[04] = -file=E:\usr\sap\BWT\DVEBMGS10\SDM\program\config\sdm_jstartup.properties
-> arg[05] = -syncSem=JSTARTUP_WAIT_ON_3548
-> arg[06] = -nodeName=sdm
-> arg[07] = -jvmOutFile=E:\usr\sap\BWT\DVEBMGS10\work\jvm_sdm.out
-> arg[08] = -jvmOutMode=append
-> arg[09] = -stdOutFile=E:\usr\sap\BWT\DVEBMGS10\work\std_sdm.out
-> arg[10] = -stdOutMode=append
-> arg[11] = -traceMode=append
-> arg[12] = -locOutFile=E:\usr\sap\BWT\DVEBMGS10\work\dev_sdm
-> arg[13] = -mode=JCONTROL
-> arg[14] = pf=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[15] = -DSAPSTART=1
-> arg[16] = -DCONNECT_PORT=1373
-> arg[17] = -DSAPSYSTEM=10
-> arg[18] = -DSAPSYSTEMNAME=BWT
-> arg[19] = -DSAPMYNAME=bwtraining_BWT_10
-> arg[20] = -DSAPPROFILE=E:\usr\sap\BWT\SYS\profile\BWT_DVEBMGS10_bwtraining
-> arg[21] = -DFRFC_FALLBACK=ON
-> arg[22] = -DFRFC_FALLBACK_HOST=localhost
-> lib path = PATH=C:\j2sdk1.4.2_12\jre\bin\server;C:\j2sdk1.4.2_12\jre\bin;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\S
-> exe path = PATH=C:\j2sdk1.4.2_12\bin;E:\usr\sap\BWT\DVEBMGS10\j2ee\os_libs;F:\oracle\BWT\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS
[Thr 520] JControlICheckProcessList: process SDM started (PID:5084)
[Thr 520] Thu Aug 21 04:42:20 2008
[Thr 520] JControlICheckProcessList: process dispatcher (pid:6108) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process dispatcher
[Thr 520] JControlIResetProcess: [dispatcher] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
[Thr 520] JControlICheckProcessList: process server0 (pid:2916) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process server0
[Thr 520] JControlIResetProcess: [server0] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta
[Thr 520] JControlICheckProcessList: process SDM (pid:5084) died (RUN-FLAG)
[Thr 520] JControlIResetProcess: reset process SDM
[Thr 520] JControlIResetProcess: [SDM] not running -> increase error count (4)
[Thr 520] JControlICheckProcessList: running flight recorder:
#C:\j2sdk1.4.2_12\bin\java -classpath ../j2ee/cluster/bootstrap/sap.comtcbloffline_launcherimpl.jar com.sap.engine.offline.OfflineToolSta

Similar Messages

  • Sap J2EE Engine is not visible in NWDS

    Hi ,
    iam new to Sap iam Builing an Simple Application in Which SAP J2EE engine is not visible under
    Window ->Preferences
    can any one help me ASAP.

    MY Sap J2EE Engine is Install in Remote Host  and iam not getting the option Of SapJ2EE
    Engine in Window->Prefrences.
    iam building an Webdynpro Application In Netweaver.
    1) When i Click Deploy NewArchive and Run.
    2) Sap J2ee engine login Screen Come i logged in.
    3) But after deployment is finish.
    Iam getting an Error Saying that:
    ERROR:
    com.sap.ide.eclipse.deployer.api.APIException: ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
    Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.
         at com.sap.ide.eclipse.deployer.dc.DCClientImpl.<init>(DCClientImpl.java:70)
         at com.sap.ide.eclipse.deployer.dc.DCClientFactoryImpl.createClient(DCClientFactoryImpl.java:142)
         at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:201)
         at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:359)
         at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:149)
         at com.sap.ide.webdynpro.archivebuilder.ActionDeployArchive$DeployJob.run(ActionDeployArchive.java:214)
         at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    can you please help me with is error.

  • J2EE Engine is not starting

    Hi Experts,
    our J2EE Engine is not starting. After application restart in SAP MMC's process list for disp+work.exe the status is yellow (Running, Message Server connectionok, ...., J2EE: Some processes running). In the J2EE Process table the server0 is stopped. He tries to start it a couple of times, but after all it stopps with exitcode -11113. So I've checked the dev_trace, the entry was:
    [Thr 2376] Wed Nov 17 15:41:35 2010
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.box.number=EI3DVEBMGS00chopin] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.en.host=chopin] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx.c   841]
    [Thr 2376] *** WARNING => INFO: Unknown property [instance.system.id=0] [jstartxx.c   841]
    [Thr 1128] Wed Nov 17 15:45:06 2010
    [Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    [Thr 1128] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 1128] JLaunchISetClusterId: set cluster id 2121050
    [Thr 1128] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
    [Thr 1128] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
    [Thr 5284] Wed Nov 17 15:45:34 2010
    [Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.mw.rfc.driver.CpicDriver
    [Thr 5284] JHVM_RegisterNatives: registering methods in com.sap.i18n.cp.ConverterJNI
    [Thr 5900] JLaunchIExitJava: exit hook is called (rc = -11113)
    [Thr 5900] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 5900] JLaunchCloseProgram: good bye (exitcode = -11113)
    So I searched a little and found this [Thread|Restart of J2EE Engine] and modified the Heapsize. As our Server is a 32-bit machine I used this sizes:
    Max heap size: 1024M
    -Xms1024M // old size: 512
    -XX:PermSize=512M // old size: 128
    -XX:MaxPermSize=512M // old size: 128
    -XX:NewSize=320M // old size: 86
    -XX:MaxNewSize=320M // old size: 86
    The result was another error message in dev_trace:
    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    [Thr 2396] JLaunchIAbortJava: abort hook is called
    [Thr 2396] **********************************************************************
    ERROR => The Java VM aborted unexpectedly.
    Please see SAP Note 943602 , section 'Java VM crashes'
    for additional information and trouble shooting.
    [Thr 2396] JLaunchCloseProgram: good bye (exitcode = -2)
    ok, so I changed the sizes again to:
    Max heao size: 1024M
    -XX:MaxPermSize=128M
    -XX:PermSize=512M
    -Xms512M
    -XX:NewSize=320M
    -XX:MaxNewSize=86M
    But there's still the same error occurring.
    Please, does someone has an idea how to solve this issue?
    Thanks in advance,
    Tan

    Hi Desiree,
    thank you for your posting. It's getting better, but it's still not running. I've set up the same password in client 001 and in the java ume and restarted the cluster. When starting the server0 is J2EE Process Table is starting framework, then starting apps, but after something about 9 minutes its restarting, but it seems not to have errors (in the J2EE Process Table there are restarts displayed but no errors. So its better than before where the server0 restarts after 30 seconds and stopps restarting after 3 errors and 4 restarts.
    But nows he's restarting and restarting....
    In TA SMICM there is the J2EE server operational TRUE which was not before. When checking the RFC Destination there comes the status "not ready" during Starting framework phase and status "Service unavailable" during starting apps phase.
    Here are some parts of the dev_trave:
    "VM Thread" prio=5 tid=0x003cec80 nid=0x1028 runnable
    "Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x7e0 runnable
    [Thr 4136] JLaunchIExitJava: exit hook is called (rc = 666)
    [Thr 4136] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 4136] JLaunchCloseProgram: good bye (exitcode = 666)
    "VM Thread" prio=5 tid=0x003cec80 nid=0xb50 runnable
    "VM Periodic Task Thread" prio=10 tid=0x011dcc88 nid=0x9e4 waiting on condition
    "Suspend Checker Thread" prio=10 tid=0x011d8038 nid=0x748 runnable
    [Thr 2896] Thu Nov 18 09:13:33 2010
    [Thr 2896] JLaunchIExitJava: exit hook is called (rc = 666)
    [Thr 2896] **********************************************************************
    ERROR => The Java VM terminated with a non-zero exit code.
    Please see SAP Note 943602 , section 'J2EE Engine exit codes'
    for additional information and trouble shooting.
    [Thr 2896] JLaunchCloseProgram: good bye (exitcode = 666)
    ... and so on.
    I'm not sure whether I should change or add entries in the configtool.bat like in your link recommended. The Engine was running with this settings before.....

  • J2EE Engine does not start

    Hi All.
    I installed a Dialog instance.
    After the installation of the license key on the central instance, the dialog J2EE Engine does not start anymore.
    Here it is the std_server0.out log:
    stdout/stderr redirect
    node name   : server0
    pid         : 1298548
    system name : PRP
    system nr.  : 10
    started at  : Mon Sep  3 19:07:54 2007
    [Thr  1] Mon Sep  3 19:07:55 2007
    [Thr  1] MtxInit: -2 0 0
    JVMST080: verbosegc is enabled
    JVMST082: -verbose:gc output will be written to stderr
    ^MSAP J2EE Engine Version 7.00   PatchLevel is starting...
    ^M
    Loading: LogManager ... 1887 ms.
    Loading: PoolManager ... 3 ms.
    Loading: ApplicationThreadManager ... 452 ms.
    Loading: ThreadManager ... 428 ms.
    Loading: IpVerificationManager ... 16 ms.
    Loading: ClassLoaderManager ... 16 ms.
    Loading: ClusterManager ... 392 ms.
    Loading: LockingManager ... 140 ms.
    Loading: ConfigurationManager ... 4656 ms.
    Loading: LicensingManager ... 28 ms.
    Loading: CacheManager ... 311 ms.
    Loading: ServiceManager ...
    <AF[1]: Allocation Failure. need 536 bytes, 0 ms since last AF>
    <AF[1]: managing allocation failure, action=0 (959472304/1073740288)>
      <GC(1): GC cycle started Mon Sep  3 19:08:13 2007
      <GC(1): freed 64170704 bytes, 95% free (1023643008/1073740288), in 136 ms>
      <GC(1): mark: 123 ms, sweep: 13 ms, compact: 0 ms>
      <GC(1): refs: soft 0 (age >= 32), weak 0, final 475, phantom 0>
    <AF[1]: completed in 159 ms>
    Loading services.:
      Service cross started. (72 ms).
      Service file started. (156 ms).
      Service memory started. (160 ms).
      Service userstore started. (24 ms).
      Service timeout started. (51 ms).
      Service runtimeinfo started. (8 ms).
      Service trex.service started. (90 ms).
      Service jmx_notification started. (77 ms).
      Service p4 started. (182 ms).
      Service classpath_resolver started. (99 ms).
      Service deploy started. (9491 ms).
      Service MigrationService started. (28 ms).
      Service bimmrdeployer started. (6 ms).
      Service log_configurator started. (21621 ms).
      Service locking started. (3 ms).
      Service http started. (772 ms).
      Service naming started. (1518 ms).
      Service failover started. (23 ms).
      Service appclient started. (29 ms).
      Service javamail started. (87 ms).
      Service ts started. (70 ms).
      Service jmsconnector started. (80 ms).
      Service licensing started. (10 ms).
      Service iiop started. (141 ms).
      Service connector started. (119 ms).
      Service configuration started. (31 ms).
      Service webservices started. (463 ms).
      Service dbpool started. (8765 ms).
    Sep 3, 2007 6:08:47 PM          com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of UME
    persistence adapter "PRIVATE_DATASOURCE" failed.
      service com.sap.security.core.ume.service ================= ERROR =================
    Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
            ume.db.connection_pool_type=SAP/BC_UME
            ume.db.connection_pool.j2ee.xatransactions_used=false
            ume.db.connection_pool.j2ee.is_unicode=FALSE
            ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
            at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
            ... 6 more
    com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: null
            ume.db.connection_pool_type=SAP/BC_UME
            ume.db.connection_pool.j2ee.xatransactions_used=false
            ume.db.connection_pool.j2ee.is_unicode=FALSE
            ume.db.connection_pool.j2ee.oracle_native_driver_used=false: (No text available)
            at com.sap.security.core.persistence.datasource.imp.DataBasePersistence.init(DataBasePersistence.java:865)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
            ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 3, 2007 6:08:47 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was
    invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Anyone can help?
    Thanks,
    Marco

    Hi all,
    after some corrections, now the problem is changed.
    Here you can find the std_server0.out:
    <b>com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='UME i
    nitialization failed.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key UME initialization f
    ailed.
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:379)
            at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
            at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
            at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
            at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
            at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)
            at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)
    Caused by: com.sap.security.core.persistence.datasource.PersistenceException: Connect to SAP gateway failed
    Connect_PM  TYPE=A ASHOST=SAPPRP-DB SYSNR=10 GWHOST=SAPPRP-DB GWSERV=sapgw10 PCS=1
    LOCATION    CPIC (TCP/IP) on local host with Unicode
    ERROR       partner 'SAPPRP-DB:sapgw10' not reached
    TIME        Fri Sep  7 15:01:11 2007
    RELEASE     700
    COMPONENT   NI (network interface)
    VERSION     38
    RC          -10
    MODULE      nixxi.cpp
    LINE        2764
    DETAIL      NiPConnect2
    SYSTEM CALL connect
    ERRNO       79
    ERRNO TEXT  A remote host refused an attempted connect operation.
    COUNTER     1
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:178)
            at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:446)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:363)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
            at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
            at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:222)
            at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:286)
            ... 6 more
    [Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
    Sep 7, 2007 2:01:11 PM              com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_55] Fatal: Critical shutdown was
    invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.</b>
    Thanks all,
    Marco

  • J2EE Engine is not Running

    Hi All:
    I start my XI server and found the J2EE Engine is not running what will be the main cause of this?? I tried to open the  Visula Admin but it is throwing an Error <i>Defult user parametes not find</i>
    What can be the cause of it??
    Thanks
    Farooq.

    Hi Farooq,
    For queries regarding user name and password, Please refer the page no 16 of the following pdf:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0e1ba1a-e86e-2910-ee83-b73b54abc7d4
    I hope this helps.
    Regards,
    Shibani
    *Reward with points if helpful*

  • SAP j2ee engine is not running error while applying patches.

    Hi all,
    Iam in the process of aplpying patches using JSPM tool , for some of them iam getting the error messages , when i checked the log file for this tool it says:
    SAP J2ee engine is not running , unable to login to  <HOST name> with id <Login id>.
    Iam very new to this activity ,can anybody help me in this regard , i wil be very thankful.
    Thanks and Regards.
    Niyati.

    Hi,
    What exactly do you see when you say that the status in the MMC is OK? I don't think it can be green if you say that you get a message saying "Service Unavailable" when you try to login. If you get that message, it means that the service hasn't either been started or could not be started in case of an error. In this case the server status in the MMC should be yellow (or gray in case none of the services could be started)...
    Could you perhaps check it again? Another point to check would be if the connection to the database is OK. If you are using MySQL MaxDB, you could use the Database Manager tool to check this. Sometimes the log files fill up the database and the server cannot start because the database is full. In such cases you will need to clear the logs and then restart the entire cluster.
    Sameer

  • J2EE engine will not start

    Hi experts.
    J2EE engine will not start.  Below is the lower section of the trace.  I'd appreciate help with interpretation as I am a NW newby.
    I just installed an J2EE key in tcode SLICENSE for our developer's subscription NW 7.0 instance.  Another thread implied installing the J2EE key in visual administrator, but how is that possible if the J2EE engine is not running?  I cannot establish a connection.
    Thanks,
    Aron
    DpJ2eeStart: j2ee state = STARTED
    rdisp/http_min_wait_dia_wp : 1 -> 1
    ***LOG CPS=> DpLoopInit, ICU ( 3.0 3.0 4.0.1) [dpxxdisp.c   1633]
    ***LOG Q0K=> DpMsAttach, mscon ( S-SAPDEV01) [dpxxdisp.c   11822]
    DpStartStopMsg: send start message (myname is >S-SAPDEV01_DS1_00                       <)
    DpStartStopMsg: start msg sent
    CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
    CCMS: Initalizing shared memory of size 60000000 for monitoring segment.
    Tue Jul 08 13:43:35 2008
    CCMS: start to initalize 3.X shared alert area (first segment).
    DpMsgAdmin: Set release to 7000, patchlevel 0
    MBUF state PREPARED
    MBUF component UP
    DpMBufHwIdSet: set Hardware-ID
    ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c   1050]
    DpMsgAdmin: Set patchno for this platform to 146
    Release check o.K.
    DpJ2eeLogin: j2ee state = CONNECTED
    Tue Jul 08 13:43:37 2008
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
    ERROR => NiIRead: SiRecv failed for hdl 4 / sock 236
        (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4027) [nixxi.cpp    4424]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5508)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    MBUF state ACTIVE
    Tue Jul 08 13:43:38 2008
    DpModState: change server state from STARTING to ACTIVE
    Tue Jul 08 13:44:14 2008
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 3412
      argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=64998
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=DS1
      argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
      argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Tue Jul 08 13:44:17 2008
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
    ERROR => NiIRead: SiRecv failed for hdl 6 / sock 668
        (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4095) [nixxi.cpp    4424]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3412)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Tue Jul 08 13:44:34 2008
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 5156
      argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=64997
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=DS1
      argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
      argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Tue Jul 08 13:44:37 2008
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
    ERROR => NiIRead: SiRecv failed for hdl 4 / sock 208
        (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4105) [nixxi.cpp    4424]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=5156)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN
    Tue Jul 08 13:44:54 2008
    J2EE server info
      start = TRUE
      state = STARTED
      pid = 6072
      argv[0] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
      argv[1] = D:\usr\sap\DS1\DVEBMGS00\exe\jcontrol.EXE
      argv[2] = pf=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
      argv[3] = -DSAPSTART=1
      argv[4] = -DCONNECT_PORT=64996
      argv[5] = -DSAPSYSTEM=00
      argv[6] = -DSAPSYSTEMNAME=DS1
      argv[7] = -DSAPMYNAME=S-SAPDEV01_DS1_00
      argv[8] = -DSAPPROFILE=D:\usr\sap\DS1\SYS\profile\DS1_DVEBMGS00_S-SAPDEV01
      argv[9] = -DFRFC_FALLBACK=ON
      argv[10] = -DFRFC_FALLBACK_HOST=localhost
      start_lazy = 0
      start_control = SAP J2EE startup framework
    DpJ2eeStart: j2ee state = STARTED
    DpJ2eeLogin: j2ee state = CONNECTED
    Tue Jul 08 13:44:57 2008
    ***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4424]
    ERROR => NiIRead: SiRecv failed for hdl 6 / sock 200
        (SI_ECONN_BROKEN/10054; I4; ST; 127.0.0.1:4117) [nixxi.cpp    4424]
    DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
    DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=6072)
    ERROR => DpProcKill: kill failed [dpntdisp.c   371]
    DpIJ2eeShutdown: j2ee state = SHUTDOWN

    Actually it was to remove compression, not to allow archiving.  Sorry!
    We're using Windows Server 2003.  Right-click on a folder or file, choose Properties.  Click on the Advanced button on the General tab.  Remove the check box for Compress to save disk space, click ok.  When you click on Apply there will be a prompt to apply just to that folder only or on subfolders and files as well.
    When compression is applied, the text for the folder turns blue.  When is not applied, the text is black.

  • SAP J2EE Engine : does not work !!!

    Hi everyone,
    I have installed SAP NW2004s Java SP9 Trial (on Windows XP and Sapdb as database). The installation finished without problems.
    But when I start my SAP system, the SAP J2EE engine (process <b>jcontrol</b>) is still stopped
    [... I have already searched in the forum, but I have not found a solution to my problem ...]
    Here is the contents of files <b>dev_jcontrol</b> & <b>dev_sdm</b> :
    File <b>dev_jcontrol</b> : *************************************
    trc file: "D:\usr\sap\J2E\JC01\work\dev_jcontrol", trc level: 1, release: "700"
    node name   : jcontrol
    pid         : 1384
    system name : J2E
    system nr.  : 01
    started at  : Mon Dec 03 15:23:56 2007
    arguments       :
           arg[00] : D:\usr\sap\J2E\JC01\exe\jcontrol.EXE
           arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
    [Thr 2356] Mon Dec 03 15:23:56 2007
    [Thr 2356] *** <b>ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] [jstartxx.c   725]
    [Thr 2356] *** ERROR => Can't open property file [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties] </b>[jstartxx.c   1952]
    [Thr 2356] *** ERROR => JStartupReadArgumentsEx: can't enumerate nodes [D:\usr\sap\J2E\JC01\j2ee\cluster\instance.properties;D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties] (rc = -1) [jstartxx.c   524]
    File <b>dev_sdm</b> : *************************************
    trc file: "D:\usr\sap\J2E\JC01\work\dev_sdm", trc level: 1, release: "700"
    node name   : sdm
    pid         : 1360
    system name : J2E
    system nr.  : 01
    started at  : Fri Nov 30 10:38:29 2007
    arguments       :
           arg[00] : D:\usr\sap\J2E\JC01\exe\jlaunch.exe
           arg[01] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
           arg[02] : -DSAPINFO=J2E_01_sdm
           arg[03] : pf=D:\usr\sap\J2E\SYS\profile\J2E_JC01_ahassaine
    JStartupReadInstanceProperties: read instance properties [D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties]
    -> ms host    : ahassaine
    -> ms port    : 3900
    -> OS libs    : D:\usr\sap\J2E\JC01\exe
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
    Instance properties
    -> ms host    : ahassaine
    -> ms port    : 3900
    -> os libs    : D:\usr\sap\J2E\JC01\exe
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    Worker nodes
    -> [00] sdm                  : D:\usr\sap\J2E\JC01\SDM\program\config\sdm_jstartup.properties
    [Thr 3544] Fri Nov 30 10:38:29 2007
    [Thr 3544] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr 3544] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 2240] JLaunchRequestFunc: Thread 2240 started as listener thread for np messages.
    [Thr 3352] WaitSyncSemThread: Thread 3352 started as semaphore monitor thread.
    [Thr 3544] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr 3544] CPIC (version=700.2005.12.02)
    [Thr 3544] INFO: Invalid property value [Debbugable=yes]
    [Thr 3544] [Node: SDM] java home is set by profile parameter
         Java Home: C:\Java\
    [Thr 3544] <b>JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\J2E\JC01\exe\jvmx.jar</b>
    JStartupIReadSection: read node properties [sdm]
    -> node name          : SDM
    -> node type          : sdm
    -> node execute       : yes
    -> java path          : C:\Java\
    -> java parameters    :
    -> java vm version    : 1.4.2_09-b05
    -> java vm vendor     : Java HotSpot(TM) Server VM (Sun Microsystems Inc.)
    -> java vm type       : server
    -> java vm cpu        : x86
    -> heap size          : 512M
    -> root path          : D:\usr\sap\J2E\JC01\SDM\program
    -> class path         : D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
    -> OS libs path       : D:\usr\sap\J2E\JC01\exe
    -> main class         : SDMInternal
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar
    -> shutdown class     : com.sap.sdm.jstartup.shutdown.InternalShutDown
    -> parameters         : server sdmhome=D:\usr\sap\J2E\JC01\SDM\program
    -> debuggable         : yes
    -> debug mode         : no
    -> debug port         : 50000
    -> shutdown timeout   : 120000
    [Thr 3544] JLaunchISetDebugMode: set debug mode [no]
    [Thr 2480] JLaunchIStartFunc: Thread 2480 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [SDM]
    -> stack   : 262144 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Dsys.global.dir=D:\usr\sap\J2E\SYS\global
    -> arg[  4]: -Dapplication.home=D:\usr\sap\J2E\JC01\exe
    -> arg[  5]: -Djava.class.path=D:\usr\sap\J2E\JC01\exe\jstartup.jar;D:\usr\sap\J2E\JC01\exe\jvmx.jar;D:\usr\sap\J2E\JC01\SDM\program\bin\SDM.jar
    -> arg[  6]: -Djava.library.path=C:\Java
    jre\bin\server;C:\Java
    jre\bin;C:\Java
    bin;D:\usr\sap\J2E\JC01\exe;d:\sapdb\programs\bin;d:\sapdb\programs\pgm;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;D:\usr\sap\J2E\SYS\exe\uc\NTI386
    -> arg[  7]: -Dmemory.manager=512M
    -> arg[  8]: -Xmx512M
    -> arg[  9]: -DLoadBalanceRestricted=no
    -> arg[ 10]: -Djstartup.mode=JCONTROL
    -> arg[ 11]: -Djstartup.ownProcessId=1360
    -> arg[ 12]: -Djstartup.ownHardwareId=G1610100576
    -> arg[ 13]: -Djstartup.whoami=sdm
    -> arg[ 14]: -Djstartup.debuggable=yes
    -> arg[ 15]: -DSAPINFO=J2E_01_sdm
    -> arg[ 16]: -DSAPSTARTUP=1
    -> arg[ 17]: -DSAPSYSTEM=01
    -> arg[ 18]: -DSAPSYSTEMNAME=J2E
    -> arg[ 19]: -DSAPMYNAME=ahassaine_J2E_01
    -> arg[ 20]: -DSAPDBHOST=ahassaine
    -> arg[ 21]: -Dj2ee.dbhost=ahassaine
    CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
    CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
    CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
    CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
    CompilerOracle: exclude iaik/security/md/SHA a
    CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
    CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
    CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
    [Thr 2480] JHVM_LoadJavaVM: Java VM created OK.
    JHVM_BuildArgumentList: main method arguments of node [SDM]
    -> arg[  0]: server
    -> arg[  1]: sdmhome=D:\usr\sap\J2E\JC01\SDM\program
    [Thr 2240] Fri Nov 30 10:38:33 2007
    [Thr 2240] JLaunchRequestFunc: receive command:17, argument:0 from pid:2600
    [Thr 2240] JLaunchIShutdownInvoke: set shutdown interval (stop:1196419113/end:1196419233/TO:120)
    [Thr 2240] JLaunchProcessCommand: Invoke VM Shutdown
    [Thr 2240] JHVM_FrameworkShutdownDirect: invoke direct shutdown
    [Thr 2240] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
    [Thr 2240] JLaunchISetState: change state from [Initial (0)] to [Stopping (5)]
    [Thr 640] Fri Nov 30 10:38:34 2007
    [Thr 640] JLaunchIExitJava: exit hook is called (rc = 0)
    [Thr 640] JLaunchCloseProgram: good bye (exitcode = 0)
    Thank you very much in advance for your help.
    Hassan

    Hi!
    If instance.properties is not there your installation has not finished correctly. This file is the central point of information for the bootstrap, which retrieves the info on how to connect to the database to collect the infos for the system startup (which will then overwrite your instance.properties file with the most recent values from the DB).
    Please check if instance.properties has been deleted and can maybe be restored from tape or if there was an error in the installation.
    Regards,
    Jörg

  • J2ee engine does not start up after system copy

    Dear All,
    I have done a system copy of BW3.5 (NW04). I installed the BW.3.5 and then replaced the data and control files.
    This has ABAP + java.
    Now after system copy when i am starting the server, the J2ee instance doesnt start up.
    ABAP is running and DB is up too.
    I am getting the following error in log_bootstrap file:-
    Exception occured:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    ==[ Caused by: ]==----
    com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID1125100) in the database! Check
    database consistency or local Bootstrap properties!
            at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:81)
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    [Aug 26, 2008 2:00:26 PM ] [Bootstrap module]> Problem occured while performing synchronization.
    [Aug 26, 2008 2:00:42 PM ] -
    [Aug 26, 2008 2:00:42 PM ] Bootstrap MODE:
    [Aug 26, 2008 2:00:42 PM ] <INSTANCE GLOBALS>
    [Aug 26, 2008 2:00:42 PM ]  determined by parameter [ID0011251].
    [Aug 26, 2008 2:00:42 PM ] -
    [Aug 26, 2008 2:00:46 PM ] Exception occured:
    com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/di
    spatcher/ID1125100" does not exist.
            at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getSubConfiguration(Configura
    tionDataCacheAllImpl.java:107)
            at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfi
    guration.java:715)
            at com.sap.engine.bootstrap.Synchronizer.getConfiguration(Synchronizer.java:365)
            at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:78)
            at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
            at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
            at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:813)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
            at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
            at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
            at java.lang.reflect.Method.invoke(Method.java:391)
            at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    What could the problem?. Do I need to do some other settings for system copy of JVA instance?
    Kindly help
    Thanks
    Tajinder

    Hi,
    I already checked that note. It did not help.
    I am pasting mine dev_jcontrol file:--
    trc file: "/usr/sap/BD1/DVEBMGS00/work/dev_jcontrol", trc level: 1, release: "640"
    node name   : jcontrol
    pid         : 868524
    system name : BD1
    system nr.  : 00
    started at  : Tue Aug 26 16:27:10 2008
    arguments   :
        arg[00] : jcontrol
        arg[01] : pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
        arg[02] : -DSAPSTART=1
        arg[03] : -DCONNECT_PORT=64380
        arg[04] : -DLISTEN_PORT=64381
        arg[05] : -DSAPSYSTEM=00
        arg[06] : -DSAPSYSTEMNAME=BD1
        arg[07] : -DSAPMYNAME=BWQAS_BD1_00
        arg[08] : -DSAPPROFILE=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
        arg[09] : -DFRFC_FALLBACK=ON
        arg[10] : -DFRFC_FALLBACK_HOST=localhost
    JStartupReadInstanceProperties: read instance properties [/usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.proper
    ties:/usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties]
    -> ms host    : BWQAS
    -> ms port    : 3601
    -> OS libs    : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> files [01] : /usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties
    Instance properties
    -> ms host    : BWQAS
    -> ms port    : 3601
    -> os libs    : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs
    -> admin URL  :
    -> run mode   : NORMAL
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID1125100  : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID1125150  : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID1125100            : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> [01] ID1125150            : /usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> [02] sdm                  : /usr/sap/BD1/DVEBMGS00/SDM/program/config/sdm_jstartup.properties
    [Thr 01] Tue Aug 26 16:27:10 2008
    [Thr 01] SigISetDefaultAction : default handling for signal 20
    [Thr 01] JControlExecuteBootstrap: execute bootstrap process [bootstrap]
    [Thr 258] JControlDPMessageFunc: Thread 258 started as handler thread for R/3 dispatcher messages.
    [Thr 01] *** WARNING => Maximum Java heap size specified twice (through maxHeapSize and in javaParameters) -
    using -Xmx512m [jstartxx_mt. 2282]
    [Thr 01] [Node: bootstrap] java home is set by profile parameter
            Java Home: /usr/java14_64
    JStartupIReadSection: read node properties [bootstrap]
    -> node name       : bootstrap
    -> node type       : bootstrap
    -> java path       : /usr/java14_64
    -> java parameters : -Djco.jarm=1 -Djco.jarm=1
    -> java vm version : J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20060421 (SR5) (JIT enabl
    ed: jitc)
    -> java vm vendor  : Classic VM (IBM Corporation)
    -> java vm type    : <default>
    -> java vm cpu     : ppc64
    -> heap size       : 512M
    -> root path       : /usr/sap/BD1/DVEBMGS00/j2ee/cluster
    -> class path      : ./bootstrap/launcher.jar
    -> OS libs path    : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs
    -> main class      : com.sap.engine.offline.OfflineToolStart
    -> framework class : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class  : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path  : /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jstartup.jar
    -> parameters      : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0011251
    -> debuggable      : yes
    -> debug mode      : no
    -> debug port      : 60000
    -> shutdown timeout: 120000
    JStartupStartJLaunch: program = /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jlaunch
    -> arg[00] = /usr/sap/BD1/DVEBMGS00/j2ee/os_libs/jlaunch
    -> arg[01] = pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
    -> arg[02] = -DSAPINFO=BD1_00_bootstrap
    -> arg[03] = -file=/usr/sap/BD1/DVEBMGS00/j2ee/cluster/instance.properties
    -> arg[04] = -nodeName=bootstrap
    -> arg[05] = -nodeId=-1
    -> arg[06] = -syncSem=12582961
    -> arg[07] = -jvmOutFile=/usr/sap/BD1/DVEBMGS00/work/jvm_bootstrap.out
    -> arg[08] = -stdOutFile=/usr/sap/BD1/DVEBMGS00/work/std_bootstrap.out
    -> arg[09] = -locOutFile=/usr/sap/BD1/DVEBMGS00/work/dev_bootstrap
    -> arg[08] = -stdOutFile=/usr/sap/BD1/DVEBMGS00/work/std_bootstrap.out
    -> arg[09] = -locOutFile=/usr/sap/BD1/DVEBMGS00/work/dev_bootstrap
    -> arg[10] = -mode=BOOTSTRAP
    -> arg[11] = pf=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
    -> arg[12] = -DSAPSTART=1
    -> arg[13] = -DCONNECT_PORT=64382
    -> arg[14] = -DLISTEN_PORT=64381
    -> arg[15] = -DSAPSYSTEM=00
    -> arg[16] = -DSAPSYSTEMNAME=BD1
    -> arg[17] = -DSAPMYNAME=BWQAS_BD1_00
    -> arg[18] = -DSAPPROFILE=/usr/sap/BD1/SYS/profile/BD1_DVEBMGS00_BWQAS
    -> arg[19] = -DFRFC_FALLBACK=ON
    -> arg[20] = -DFRFC_FALLBACK_HOST=localhost
    -> lib path = LIBPATH=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/B
    D1/DVEBMGS00/j2ee/os_libs:/usr/sap/BD1/SYS/exe/run:/usr/sap/BD1/SYS/exe/runU:/usr/lib:/usr/sap/BD1/DVEBMGS00/
    j2ee/os_libs:/usr/sap/BD1/DVEBMGS00/j2ee/os_libs:/usr/lib:/lib:/usr/sap/BD1/SYS/exe/run:/usr/sap/BD1/SYS/exe/
    runU
    -> exe path = PATH=/usr/java14_64/bin:/usr/sap/BD1/DVEBMGS00/j2ee/os_libs:/oracle/BD1/920_64/bin:/usr/java14_
    64/bin:/home/bd1adm:/usr/sap/BD1/SYS/exe/runU:/usr/sap/BD1/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/home
    /bd1adm/bin:/usr/bin/X11:/sbin:.
    [Thr 01] JStartupICreateProcess: fork process (pid 893002)
    [Thr 01] Tue Aug 26 16:27:18 2008
    [Thr 01] *** ERROR => invalid return code of process [bootstrap] (exitcode=66) [jstartxx_mt. 1433]
    [Thr 01] JControlExecuteBootstrap: error executing bootstrap node [bootstrap] (rc=66)
    [Thr 01] JControlCloseProgram: started (exitcode = 66)
    [Thr 01] JControlCloseProgram: good bye... (exitcode=66)
    DO i have to change the some settingdsin any file for java instance after system copy.
    Thanks
    Tajinder

  • J2EE engine does not start correctly

    hi,
    after the installation of sap was v6.40 abap & j2ee, i cannot logon to the j2ee engine as described in the documentation. when i will access the engine by using a web browser, i get the following error message:
    "503: Service Unavailable"
    i had a look on the log files and found these messages in the server log file:
    java.rmi.RemoteException: Error occurred while starting applications; nested exception is:
         com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Container EJBContainer is not active at the moment and it is not possible to startApp sap.com/com.sap.lcrabapapi.
         at ...
    there are more lines with error messages which seems to belong to the original problem with the ejbcontainer.
    can anyone tell me how to fix the errors?
    thanks in advance,
    michael keller

    Hi,
    See note: 535532
    Mid way through the note it says:
    You can then register the SAP J2EE Engine as a windows-service by using the SAP J2EE Engine Config Tool. Open a command prompt and change to the directory <J2EE Engine installation directory>configtool and run configtool.bat or start this tool via your Start-Menu "Tools->Config Tool" of the J2EE Server entry. Select at the left navigation area of this tool the entry "cluster/ server" the checkbox "Enabled" at the tabstrip "NT Service". Apply these settings by clicking on "File->Apply" at the menu. Do the same with the entry "cluster / dispatcher".
    After you have finished these steps you can register now the J2EE Engine as a windows service.
    Start service.exe, which is also located in the directory
    <J2EE Engine installation directory>configtool. It works with three
    parameters:
    Service.exe u2013install u2013 the service(s) is (are) registered as NT/2000 Service(s). For each specified cluster node, a separate service is generated. All services have startup mode automatic. To start the service(s), open the Control Panel ¨Services folder. Find the service in the list of available services (for example: SAP J2EE Server 1, SAP J2EE Dispatcher 1, SAP J2EE Server 2, and so on). Select it, and choose u201CStartu201D on the right-hand side. No u201CStartup Parametersu201D are needed for the service to run. The system starts the particular J2EE Engine 6.20 node in background mode. It can be used and administered as usual. The only difference is that the server does not run in a console window.
    There may be other notes along these lines.
    You should also check any notes on the setup of SAP in MSCS cluster, as it will contain instructions for registering the services.
    Hope this gives you a pointer in the right direction.

  • Dispatcher of J2EE Engine does not start

    I have the following problem, we restart the j2ee engine and the dispatcher does not come up. The server and SDM works fine
    <b>dev_dispatcher:</b>
    trc file: "/usr/sap/Q82/JC00/work/dev_dispatcher", trc level: 1, release: "700"
    node name   : ID2430700
    pid         : 1192142
    system name : Q82
    system nr.  : 00
    started at  : Tue Nov 20 10:47:45 2007
    arguments       :
           arg[00] : /usr/sap/Q82/JC00/exe/jlaunch
           arg[01] : pf=/usr/sap/Q82/SYS/profile/Q82_JC00_sapQ82
           arg[02] : -DSAPINFO=Q82_00_dispatcher
           arg[03] : pf=/usr/sap/Q82/SYS/profile/Q82_JC00_sapQ82
    [Thr  1] Tue Nov 20 10:47:45 2007
    [Thr  1] *** WARNING => INFO: Unknown property [instance.box.number=Q82JC00sapq82] [jstartxx_mt. 841]
    [Thr  1] *** WARNING => INFO: Unknown property [instance.en.host=sapQ82] [jstartxx_mt. 841]
    [Thr  1] *** WARNING => INFO: Unknown property [instance.en.port=3201] [jstartxx_mt. 841]
    [Thr  1] *** WARNING => INFO: Unknown property [instance.system.id=00] [jstartxx_mt. 841]
    JStartupReadInstanceProperties: read instance properties [/usr/sap/Q82/JC00/j2ee/cluster/instance.properties]
    -> ms host    : sapQ82
    -> ms port    : 3901
    -> OS libs    : /usr/sap/Q82/JC00/j2ee/os_libs
    -> Admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Used property files
    -> files [00] : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    Instance properties
    -> ms host    : sapQ82
    -> ms port    : 3901
    -> os libs    : /usr/sap/Q82/JC00/j2ee/os_libs
    -> admin URL  :
    -> run mode   : normal
    -> run action : NONE
    -> enabled    : yes
    Bootstrap nodes
    -> [00] bootstrap            : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    -> [01] bootstrap_ID2430700  : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    -> [02] bootstrap_ID2430750  : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    Worker nodes
    -> [00] ID2430700            : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    -> [01] ID2430750            : /usr/sap/Q82/JC00/j2ee/cluster/instance.properties
    [Thr  1] JLaunchRequestQueueInit: create named pipe for ipc
    [Thr  1] JLaunchRequestQueueInit: create pipe listener thread
    [Thr 258] JLaunchRequestFunc: Thread 258 started as listener thread for np messages.
    [Thr 515] WaitSyncSemThread: Thread 515 started as semaphore monitor thread.
    [Thr  1] SigISetDefaultAction : default handling for signal 20
    [Thr  1] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
    [Thr  1] CPIC (version=700.2006.09.13)
    [Thr  1] [Node: dispatcher] java home is set by profile parameter
         Java Home: /usr/java14_64
    [Thr  1] JStartupICheckFrameworkPackage: can't find framework package /usr/sap/Q82/JC00/exe/jvmx.jar
    JStartupIReadSection: read node properties [ID2430700]
    -> node name          : dispatcher
    -> node type          : dispatcher
    -> node execute       : yes
    -> jlaunch parameters :
    -> java path          : /usr/java14_64
    -> java parameters    : -Xj9 -Xgcpolicy.gencon -verbose:gc -Xmn70m -Xdisableexplicitgc -Djava.security.policy=.\java.policy -Djava.security.egd=file:/dev/urandom -Djco.jarm=1
    -> java vm version    : J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142ifx-20070510a (JIT enabled)
    -> java vm vendor     : IBM J9 VM (IBM Corporation)
    -> java vm type       : server
    -> java vm cpu        : ppc64
    -> heap size          : 202M
    -> init heap size     : 202M
    -> root path          : /usr/sap/Q82/JC00/j2ee/cluster/dispatcher
    -> class path         : ./bin/boot/boot.jar:./bin/system/bytecode.jar:.
    -> OS libs path       : /usr/sap/Q82/JC00/j2ee/os_libs
    -> main class         : com.sap.engine.boot.Start
    -> framework class    : com.sap.bc.proj.jstartup.JStartupFramework
    -> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives
    -> framework path     : /usr/sap/Q82/JC00/exe/jstartup.jar:/usr/sap/Q82/JC00/exe/jvmx.jar
    -> shutdown class     : com.sap.engine.boot.Start
    -> parameters         :
    -> debuggable         : no
    -> debug mode         : no
    -> debug port         : 50000
    -> shutdown timeout   : 120000
    [Thr  1] JLaunchISetDebugMode: set debug mode [no]
    [Thr 772] JLaunchIStartFunc: Thread 772 started as Java VM thread.
    JHVM_LoadJavaVM: VM Arguments of node [dispatcher]
    -> stack   : 1048576 Bytes
    -> arg[  0]: exit
    -> arg[  1]: abort
    -> arg[  2]: vfprintf
    -> arg[  3]: -Xj9
    -> arg[  4]: -Xgcpolicy.gencon
    -> arg[  5]: -verbose:gc
    -> arg[  6]: -Xmn70m
    -> arg[  7]: -Xdisableexplicitgc
    -> arg[  8]: -Djava.security.policy=.\java.policy
    -> arg[  9]: -Djava.security.egd=file:/dev/urandom
    -> arg[ 10]: -Djco.jarm=1
    -> arg[ 11]: -Dsys.global.dir=/usr/sap/Q82/SYS/global
    -> arg[ 12]: -Dapplication.home=/usr/sap/Q82/JC00/exe
    -> arg[ 13]: -Djava.class.path=/usr/sap/Q82/JC00/exe/jstartup.jar:/usr/sap/Q82/JC00/exe/jvmx.jar:./bin/boot/boot.jar:./bin/system/bytecode.jar:.
    -> arg[ 14]: -Djava.library.path=/usr/java14_64/jre/bin:/usr/java14_64/jre/bin:/usr/java14_64/jre/bin/classic:/usr/java14_64/jre/bin:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/sap/Q82/JC00/exe::/usr/lib:/usr/sap/Q82/JC00/j2ee/os_libs:/usr/sap/Q82/JC00/exe:/usr/sap/Q82/JC00/exe:/usr/lib:/lib:/usr/sap/Q82/SYS/exe/run:/oracle/client/10x_64/instantclient
    -> arg[ 15]: -Dmemory.manager=202M
    -> arg[ 16]: -Xmx202M
    -> arg[ 17]: -Xms202M
    -> arg[ 18]: -DLoadBalanceRestricted=no
    -> arg[ 19]: -Djstartup.mode=JCONTROL
    -> arg[ 20]: -Djstartup.ownProcessId=1192142
    -> arg[ 21]: -Djstartup.ownHardwareId=R1572408088
    -> arg[ 22]: -Djstartup.whoami=dispatcher
    -> arg[ 23]: -Djstartup.debuggable=no
    -> arg[ 24]: -DSAPINFO=Q82_00_dispatcher
    -> arg[ 25]: -DSAPSTARTUP=1
    -> arg[ 26]: -DSAPSYSTEM=00
    -> arg[ 27]: -DSAPSYSTEMNAME=Q82
    -> arg[ 28]: -DSAPMYNAME=sapQ82_Q82_00
    -> arg[ 29]: -DSAPDBHOST=sapQ82
    -> arg[ 30]: -Dj2ee.dbhost=sapQ82
    [Thr 772] *** ERROR => JHVM_LoadJavaVM: Cannot create Java VM (rc=-6) [jhvmxx_mt.c  542]
    [Thr 772] *** ERROR => Cannot load Java VM (server) (rc=-1) [jlnchxxi_mt. 752]
    [Thr 772] **********************************************************************
    ERROR => Java VM initialization failed.
    Please see SAP Note 943602 , section 'Java VM initialization issues'
    for additional information and trouble shooting.
    [Thr 772] SigISetIgnoreAction : SIG_IGN for signal 20
    [Thr 772] JLaunchCloseProgram: good bye (exitcode = -1)
    Does somebody has any ideas?
    Regards Peter

    Hi folks,
    i solved it by myself. There was a wrong javaparameter in the settings of the dispatcher.
    -Xgcpolicy.gencon instead of -Xgcpolicy:gencon, my colleague has found it out.
    Regards Peter

  • J2ee engine does not start - error 503

    have a dual stack NetWeaver installation. I can start/connect to the ABAP stack fine, but I cannot connect to the Java stack.
    When I do http://<machine name>:50000 or http://<machine name>:50000/irj/portal ... I get a "503 service unavailable. Application stopped" message.
    searching through the j2ee logs did not reveal any problems (All j2ee services look like they are started successfully).

    Tiberiu,
    Check ume service : com.sap.security.core.ume.service started or not?
    I think it may be very slow and this may cause a lot of services to time out.
    Changed settings in config tool:
    1.instance_IDXXX -> server -> managers -> Service manager -> LoadTimeout from 5 to 15.
    2.instance_IDXXX -> server -> managers -> ApplicationThreadManager there change InitialThreadCount, MinThreadCount and MaxThreadCount to 350.
    3.Restart the server.
    Regards,
    Karthick Eswaran
    *Do not forget to Reward points for helpful answers

  • SAP J2EE Engine could not found

    Hi All,
    I was trying to install java components in ECC 5.0 IDES Server. it showing an error " This Installation requires an SAP J2EE Engine version 6.30 or higher"
    and then i gave NEXT then it gave another error message " No instance found for the central instance. Check your file system. Install Web AS 6.30 and restart this deployment afterwards".
    Kindly let me know how to find which version of Web AS now i am using and how to upgrade to higher version.
    Thanks,
    Clark

    Hi
    I cannot say any thing before getting more detail. But its look that your java parameter is not set correctly.
    Check the following thing
    1- if window machine required service pack is installed.
    2- Java parameter is not missing.
    3- Environment variable are set correctly
    Thank You

  • WAS SP9 SR1 ABAP+Java Add in installation , j2EE engine is not running

    I have completely installed SAP Netweaver SP9 SR1 WAS ABAP+JAVA addin and Installed XI completely. After few days j2EE engine stops running. I have applied the license after requesting from SAP Mareketplace and applied in WAS ABAP using SLICENSE transaction.
    Issue faced
    1. Tried to connect j2ee engine home page which is showing.
    Dispatcher is running but no server connected.
    Now I have removed the WAS J2EE installation and removed the client on which WAS j2EE engine installed. After doing this I tested the WAS ABAP which is running fine. Now I am again installing WAS Java addin. Which installed success fully and have seen the j2ee engine server page running.  But proceeding further to install JAVA Dialog instance I am facing folloing issues
    2. while installation step 8 and 9 as per SAP INSTANCE GUI .
    3. And J2EE engine is again stopping.
    Can any one help me to install J2ee dialog installation and resolving these issues.
    Anand Verma
    HCL technologies

    Hi Anand,
    J2EE Engine has a separate licensing mechanism. If the temporary license expires, the server will shut down every 30 minutes. You install a permanent license using Visual Administrator in service "Licensing Adapter".
    In any case, a look into the log files of the engine can provide further information. They are found at
    .../<SID>/<INSTANCE>/j2ee/cluster/server<n>/log
    Kind regards,
    Juergen Kremp

  • J2EE engine does not start and then visual administartor gives error

    I am trying to start the SAP J2EE GUI after entering User J2EE_ADMIN and
    password it hardly goestill 5% and gives following task error:
    "com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
    create new RemoteLoginContext".
    I have also applied 701654 as suggested by you earlier but I have never
    changed the password, However I have updated the Secure storage also
    using configuration tool.

    I am trying to start the SAP J2EE GUI after entering User J2EE_ADMIN and
    password it hardly goestill 5% and gives following task error:
    "com.sap.engine.services.security.exceptions.BaseLoginException: Cannot
    create new RemoteLoginContext".
    I have also applied 701654 as suggested by you earlier but I have never
    changed the password, However I have updated the Secure storage also
    using configuration tool.

Maybe you are looking for

  • [SOLVED]Arch Linux, and Windows 8.1 Dual Boot issue

    Hi guys. I recently bought a new laptop, and decided to run Arch Linux and Windows 8.1. I installed Windows 8.1 first as recommended by the beginners guide, and then installed Arch Linux. I made sure UEFI was enabled in my BIOS, and made sure everyth

  • Windows 7 Ultimate (64-bit) Create a System Image Failure (error code: 0x80780119)

    Hello, I recently bought a new 1 TB hard drive, and I want to move everything from my original 250 GB to the new one. I have read from numerous sources that Creating a System Image through Windows 7, and then restoring that system image using the Win

  • Non-http servlet without headers

    I would like to create a servlet that does not respond to web requests, but to invocations by client sockets (on port 80). It all goes well, but even if I use a simple Servlet implementation, the web server wraps the response into a http response, an

  • No mac Only windows

    my macbook pro ran good with bootcamp windows 7 installed with OS X and then this day i turned it off after work.. the other morning i turn it on and an error comes up saying MISSING OPERATING SYSTEM.. i thought there might be some problem with the w

  • Validation for storage location

    Greetings to Experts!! I am looking for following two validations; 1- stock outward movement from a particular storage location (say ABC ) could only be possible via 351. 2- 351 movement type could only be used for storage location ABC Plz Help, Rega