cancel
Showing results for 
Search instead for 
Did you mean: 

J2EE status info unavailable

Former Member
0 Kudos


Hi All,

We have a Solution Manager 7.1 system. SP Level 15. For some reason the Java Stack will not start. The MMC shows J2EE status info unavailable. Startup is not registering anything in directory \usr\sap\SMP\DVEBMGS00\j2ee\cluster. I cannot connect to the configtool, visual admin or the offlinecfgeditor.

No users in the ABAP stack are locked.

This system has been running over a year.....nothing has been changed.

In the dev_bootstrap I see:
JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMP\DVEBMGS00\exe\jvmx.jar

(CompilerOracle read from file D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4\jre\.hotspot_compiler)
[Thr 5684] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [bootstrap]
-> arg[  0]: com.sap.engine.bootstrap.Bootstrap
-> arg[  1]: ./bootstrap
-> arg[  2]: ID0098821
**********************************************************************

[Thr 5684] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
[Thr 3936] JLaunchIExitJava: exit hook is called (rc = 66)
[Thr 3936] **********************************************************************
[Thr 3936] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 3936] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 3936] *** for additional information and trouble shooting.
[Thr 3936] **********************************************************************
[Thr 3936] JLaunchCloseProgram: good bye (exitcode = 66)

In the dev_jcontrol I see:

[Thr 4952] Wed Mar 18 09:06:47 2015

[Thr 4952] *** ERROR => invalid return code of process [bootstrap_ID9882150] (exitcode = 66) [jstartxx.c   1647]

[Thr 4952] JControlExecuteBootstrap: error executing bootstrap node [bootstrap_ID9882150] (rc = 66)

[Thr 4952] JControlCloseProgram: started (exitcode = 66)

[Thr 4952] JControlCloseProgram: good bye... (exitcode = 66)

Any ideas would be appreciated.

Thanks,

Diana

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi All. This has been resolved. IPV6 was active on the server. The Java Stack will not start while IPV6 is active. Once we deactivated it, the Java stack came up.

Thanks,

Diana

Matt_Fraser
Active Contributor
0 Kudos

That's good news. Thanks for sharing the resolution, as this is something that could easily plague someone else, too. Be sure to close out the thread as "answered" (you can mark your own answer as correct to do this).

Cheers,

Matt

Answers (1)

Answers (1)

Matt_Fraser
Active Contributor
0 Kudos

Hi Diana,

I think exitcode 66 typically means that the J2EE engine is having trouble connecting to the database, either because of an issue withe J2EE schema, the database user or password, or something with the secure store. Do you see any errors about database initialization in the bootstrap log?

Regards,

Matt

Former Member
0 Kudos

Hi Matt,

Here is my bootstrap log. How can I check my db user\pswd?


---------------------------------------------------
trc file: "dev_bootstrap", trc level: 1, release: "720"
---------------------------------------------------
node name   : bootstrap
pid         : 5996
system name : SMP
system nr.  : 00
started at  : Wed Mar 18 09:06:22 2015
arguments   :
   arg[00] : D:\usr\sap\SMP\DVEBMGS00\exe\jlaunch.exe
   arg[01] : pf=\\GMOSMLA01\sapmnt\SMP\SYS\profile\SMP_DVEBMGS00_GMOSMLA01
   arg[02] : -DSAPINFO=SMP_00_bootstrap
   arg[03] : pf=\\GMOSMLA01\sapmnt\SMP\SYS\profile\SMP_DVEBMGS00_GMOSMLA01
   arg[04] : -DSAPSTART=1
   arg[05] : -DCONNECT_PORT=49752
   arg[06] : -DSAPSYSTEM=00
   arg[07] : -DSAPSYSTEMNAME=SMP
   arg[08] : -DSAPMYNAME=GMOSMLA01_SMP_00
   arg[09] : -DSAPPROFILE=\\GMOSMLA01\sapmnt\SMP\SYS\profile\SMP_DVEBMGS00_GMOSMLA01
   arg[10] : -DFRFC_FALLBACK=ON
   arg[11] : -DFRFC_FALLBACK_HOST=localhost


**********************************************************************
Used property files
-> files [00] : D:\usr\sap\SMP\DVEBMGS00\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Bootstrap nodes
-> [00] bootstrap            : D:\usr\sap\SMP\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] bootstrap_ID9882100  : D:\usr\sap\SMP\DVEBMGS00\j2ee\cluster\instance.properties
-> [02] bootstrap_ID9882150  : D:\usr\sap\SMP\DVEBMGS00\j2ee\cluster\instance.properties
**********************************************************************

**********************************************************************
Worker nodes
-> [00] ID9882100            : D:\usr\sap\SMP\DVEBMGS00\j2ee\cluster\instance.properties
-> [01] ID9882150            : D:\usr\sap\SMP\DVEBMGS00\j2ee\cluster\instance.properties
**********************************************************************


**********************************************************************
JStartupReadInstanceProperties: read instance properties [D:\usr\sap\SMP\DVEBMGS00\j2ee\cluster\instance.properties]
-> ms host    : GMOSMLA01
-> ms port    : 3901
-> OS libs    : D:\usr\sap\SMP\DVEBMGS00\j2ee\os_libs
-> Admin URL  :
-> run mode   : normal
-> run action : NONE
-> enabled    : yes
**********************************************************************


[Thr 5324] Wed Mar 18 09:06:22 2015
[Thr 5324] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 5324] JLaunchRequestQueueInit: create pipe listener thread
[Thr 3920] JLaunchRequestFunc: Thread 3920 started as listener thread for np messages.
[Thr 5324] JLaunchInitSignalHandling: signal handling is disabled
[Thr 2164] WaitSyncSemThread: Thread 2164 started as semaphore monitor thread.
[Thr 5324] NiInit3: NI already initialized; param 'maxHandles' ignored (init=1;par=32768;cur=2048)
[Thr 5324] CCMS: Detected Double Stack (parameter "rdisp/j2ee_start" is active)
[Thr 5324] CCMS uses Shared Memory Key 73 for monitoring.
[Thr 5324] CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.
[Thr 5324] CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.
[Thr 5324] CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
[Thr 5324] CCMS: CCMS Monitoring Initialization finished, rc=0.
[Thr 5324] JStartupICheckFrameworkPackage: can't find framework package D:\usr\sap\SMP\DVEBMGS00\exe\jvmx.jar

**********************************************************************
JStartupIReadSection: read node properties [bootstrap]
-> node name          : bootstrap
-> node type          : bootstrap
-> node execute       : yes
-> java path          : D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4
-> java parameters    : -Djco.jarm=1
-> java vm version    : 4.1.016 1.6-b03
-> java vm vendor     : SAP Java Server VM (SAP AG)
-> java vm type       : server
-> java vm cpu        : amd64
-> heap size          : 256M
-> root path          : D:\usr\sap\SMP\DVEBMGS00\j2ee\cluster
-> class path         : .\bootstrap\launcher.jar
-> OS libs path       : D:\usr\sap\SMP\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     : D:\usr\sap\SMP\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMP\DVEBMGS00\exe\jvmx.jar
-> parameters         : com.sap.engine.bootstrap.Bootstrap ./bootstrap ID0098821
-> debuggable         : yes
-> debug mode         : no
-> debug port         : 60000
-> shutdown timeout   : 120 sec.
**********************************************************************

[Thr 5684] JLaunchIStartFunc: Thread 5684 started as Java VM thread.

**********************************************************************
JHVM_LoadJavaVM: VM Arguments of node [bootstrap]
-> stack   : 2097152 Bytes
-> arg[  0]: exit
-> arg[  1]: abort
-> arg[  2]: vfprintf
-> arg[  3]: -Djco.jarm=1
-> arg[  4]: -Dsys.global.dir=D:\usr\sap\SMP\SYS\global
-> arg[  5]: -Dapplication.home=D:\usr\sap\SMP\DVEBMGS00\exe
-> arg[  6]: -Djava.class.path=D:\usr\sap\SMP\DVEBMGS00\exe\jstartup.jar;D:\usr\sap\SMP\DVEBMGS00\exe\jvmx.jar;.\bootstrap\launcher.jar
-> arg[  7]: -Djava.library.path=D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\SMP\DVEBMGS00\j2ee\os_libs;D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4\jre\bin\server;D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4\jre\bin;D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4\bin;D:\usr\sap\SMP\DVEBMGS00\j2ee\os_libs;D:\usr\sap\SMP\DVEBMGS00\exe;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\;C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\;D:\usr\sap\SMP\SYS\exe\uc\NTAMD64
-> arg[  8]: -Dmemory.manager=256M
-> arg[  9]: -Xmx256M
-> arg[ 10]: -DLoadBalanceRestricted=no
-> arg[ 11]: -Djstartup.mode=BOOTSTRAP
-> arg[ 12]: -Djstartup.ownProcessId=5996
-> arg[ 13]: -Djstartup.ownHardwareId=W0567347764
-> arg[ 14]: -Djstartup.whoami=bootstrap
-> arg[ 15]: -Djstartup.debuggable=yes
-> arg[ 16]: -Xjvmx
-> arg[ 17]: -XsapSystem=00
-> arg[ 18]: -XmonGcCallback
-> arg[ 19]: -XdebugPortRange:60000-60000
-> arg[ 20]: -XdebugStateChangeCallback
-> arg[ 21]: -DSAPINFO=SMP_00_bootstrap
-> arg[ 22]: -DSAPSTART=1
-> arg[ 23]: -DCONNECT_PORT=49752
-> arg[ 24]: -DSAPSYSTEM=00
-> arg[ 25]: -DSAPSYSTEMNAME=SMP
-> arg[ 26]: -DSAPMYNAME=GMOSMLA01_SMP_00
-> arg[ 27]: -DSAPPROFILE=\\GMOSMLA01\sapmnt\SMP\SYS\profile\SMP_DVEBMGS00_GMOSMLA01
-> arg[ 28]: -DFRFC_FALLBACK=ON
-> arg[ 29]: -DFRFC_FALLBACK_HOST=localhost
-> arg[ 30]: -DSAPSTARTUP=1
-> arg[ 31]: -DSAPSYSTEM=00
-> arg[ 32]: -DSAPSYSTEMNAME=SMP
-> arg[ 33]: -DSAPMYNAME=GMOSMLA01_SMP_00
-> arg[ 34]: -DSAPDBHOST=GMOSQLPLA01
-> arg[ 35]: -Dj2ee.dbhost=GMOSQLPLA01
**********************************************************************

(CompilerOracle read from file D:\usr\sap\SMP\DVEBMGS00\exe\sapjvm_4\jre\.hotspot_compiler)
[Thr 5684] JHVM_LoadJavaVM: Java VM created OK.

**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [bootstrap]
-> arg[  0]: com.sap.engine.bootstrap.Bootstrap
-> arg[  1]: ./bootstrap
-> arg[  2]: ID0098821
**********************************************************************

[Thr 5684] JHVM_RegisterNatives: com.sap.bc.krn.perf.PerfTimes
[Thr 3936] JLaunchIExitJava: exit hook is called (rc = 66)
[Thr 3936] **********************************************************************
[Thr 3936] *** ERROR => The Java VM terminated with a non-zero exit code.
[Thr 3936] *** Please see SAP Note 943602 , section 'J2EE Engine exit codes'
[Thr 3936] *** for additional information and trouble shooting.
[Thr 3936] **********************************************************************
[Thr 3936] JLaunchCloseProgram: good bye (exitcode = 66)

Former Member
0 Kudos

My dev_disp reads:

ed Mar 18 09:06:21 2015
J2EE server info
  start = TRUE
  state = STARTED
  pid = 4400
  argv[0] = D:\usr\sap\SMP\DVEBMGS00\exe\jcontrol.EXE
  argv[1] = D:\usr\sap\SMP\DVEBMGS00\exe\jcontrol.EXE
  argv[2] = pf=\\GMOSMLA01\sapmnt\SMP\SYS\profile\SMP_DVEBMGS00_GMOSMLA01
  argv[3] = -DSAPSTART=1
  argv[4] = -DCONNECT_PORT=64989
  argv[5] = -DSAPSYSTEM=00
  argv[6] = -DSAPSYSTEMNAME=SMP
  argv[7] = -DSAPMYNAME=GMOSMLA01_SMP_00
  argv[8] = -DSAPPROFILE=\\GMOSMLA01\sapmnt\SMP\SYS\profile\SMP_DVEBMGS00_GMOSMLA01
  argv[9] = -DFRFC_FALLBACK=ON
  argv[10] = -DFRFC_FALLBACK_HOST=localhost
  start_lazy = 0
  start_control = SAP J2EE startup framework

DpJ2eeStart: j2ee state = STARTED

Wed Mar 18 09:06:22 2015
DpJ2eeLogin: j2ee state = CONNECTED

Wed Mar 18 09:06:47 2015
***LOG Q0I=> NiIRead: P=127.0.0.1:49751; L=127.0.0.1:64989: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]
*** ERROR => NiIRead: SiRecv failed for hdl 57/sock 484
    (SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:49751; L=127.0.0.1:64989) [nixxi.cpp    5087]
DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)
DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=4400)
*** ERROR => DpProcKill: kill failed [dpntdisp.c   397]
DpIJ2eeShutdown: j2ee state = SHUTDOWN

Wed Mar 18 09:07:01 2015
DpEnvCheckJ2ee: switch off j2ee start flag

Matt_Fraser
Active Contributor
0 Kudos

Is this on Oracle? I can't speak with any authority to Oracle, so maybe someone else who can will jump in. On SQL Server, however, the J2EE engine connects to the database via a schema user, i.e SAP<SID>DB, which is a database user, not an OS or domain user. So, one thing to check would be that you can connect manually to your database (via a management tool, for instance) as the schema user. The password for the schema user is stored in the secure store, which normally you can manage via the Config Tool. However, you said you can't connect to the Config Tool, either. What error do you get when starting the Config Tool?

bxiv
Active Contributor
0 Kudos

Could be a possible network issue too:


***LOG Q0I=> NiIRead: P=127.0.0.1:49751; L=127.0.0.1:64989: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 5087]

*** ERROR => NiIRead: SiRecv failed for hdl 57/sock 484

    (SI_ECONN_BROKEN/10054; I4; ST; P=127.0.0.1:49751; L=127.0.0.1:64989) [nixxi.cpp    5087]

But this could also be due to failing to auth correctly to the DB, can you pull up SDM?