cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SMDAgent not able to start ends with JVM exitcode = -11112.

Former Member

on ‎10-24-2013 11:05 AM

0 Kudos

Hi all,

i am getting the below error when i tried to start SMD Agent in SAP MMC. Please guide me to resolve this issue.

below is the system kernel version of the system

Kernel release : 720

Patch number : 46

64 bit unicode system

Below is the log of dev_SMDagent.txt

----------------------------------------------

---------------------------------------------------

trc file: "E:\usr\sap\SMD\J98\work\dev_SMDAgent", trc level: 1, release: "700"

---------------------------------------------------

node name   : smdagent

pid         : 4704

system name : SMD

system nr.  : 98

started at  : Sat Sep 28 08:18:03 2013

arguments      :

      arg[00] : E:\usr\sap\SMD\J98\..\exe\jlaunch.exe

      arg[01] : pf=E:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_ampsv03360prd

      arg[02] : -DSAPINFO=SMD_98_server

      arg[03] : pf=E:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_ampsv03360prd

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

JStartupReadInstanceProperties: read instance properties [E:\usr\sap\SMD\J98\profile\smd.properties]

-> ms host    : 

-> ms port    : 36

-> OS libs    : E:\usr\sap\SMD\exe

-> Admin URL  : 

-> run mode   : NORMAL

-> run action : NONE

-> enabled    : yes

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

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

Used property files

-> files [00] : E:\usr\sap\SMD\J98\profile\smd.properties

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

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

Instance properties

-> ms host    : 

-> ms port    : 36

-> os libs    : E:\usr\sap\SMD\exe

-> admin URL  : 

-> run mode   : NORMAL

-> run action : NONE

-> enabled    : yes

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

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

Bootstrap nodes

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

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

Worker nodes

-> [00] smdagent             : E:\usr\sap\SMD\J98\profile\smd.properties

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

[Thr 4708] Sat Sep 28 08:18:03 2013

[Thr 4708] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 4708] JLaunchRequestQueueInit: create pipe listener thread

[Thr 4764] JLaunchRequestFunc: Thread 4764 started as listener thread for np messages.

[Thr 4768] WaitSyncSemThread: Thread 4768 started as semaphore monitor thread.

[Thr 4708] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)

[Thr 4708] CPIC (version=700.2011.08.22)

[Thr 4708] INFO: Invalid property value [shutdownMethod=com.sap.smd.agent.launcher.SMDAgentLauncher.shutdown]

[Thr 4708] [Node: SMDAgent] java home is set by profile parameter

    Java Home: C:\j2sdk1.4.2_17-x64

[Thr 4708] JStartupICheckFrameworkPackage: can't find framework package E:\usr\sap\SMD\exe\jvmx.jar

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

JStartupIReadSection: read node properties [smdagent]

-> node name          : SMDAgent

-> node type          : server

-> node id            : 1

-> node execute       : yes

-> java path          : C:\j2sdk1.4.2_17-x64

-> java parameters    : -DP4ClassLoad=P4Connection 

-> java vm version    : 1.4.2_17-b06

-> java vm vendor     : Java HotSpot(TM) 64-Bit Server VM (Sun Microsystems Inc.)

-> java vm type       : server

-> java vm cpu        : amd64

-> heap size          : 128M

-> init heap size     : 128M

-> root path          : ..\SMDAgent

-> class path         : ..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar;..\..\exe\jperflib.jar;lib\patch_7.01.10.1.20110929155938\launcher\smdagentlauncher.jar

-> OS libs path       : E:\usr\sap\SMD\exe

-> main class         : com.sap.smd.agent.launcher.SMDAgentLauncher

-> framework class    : com.sap.bc.proj.jstartup.JStartupFramework

-> registr. class     : com.sap.bc.proj.jstartup.JStartupNatives

-> framework path     : E:\usr\sap\SMD\exe\jstartup.jar;E:\usr\sap\SMD\exe\jvmx.jar

-> parameters         : run jcontrol

-> debuggable         : yes

-> debug mode         : no

-> debug port         : 58981

-> shutdown timeout   : 20000

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

[Thr 4708] JLaunchISetDebugMode: set debug mode [no]

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

[Thr 4784] [JHVM_PrepareVMOptions] use java parameters set by profile parameter

    Java Parameters: -Xss2m

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

JHVM_LoadJavaVM: VM Arguments of node [SMDAgent]

-> stack   : 1048576 Bytes

-> arg[  0]: exit

-> arg[  1]: abort

-> arg[  2]: vfprintf

-> arg[  3]: -DP4ClassLoad=P4Connection

-> arg[  4]: -Dsys.global.dir=E:\usr\sap\SMD\SYS\global

-> arg[  5]: -Dapplication.home=E:\usr\sap\SMD\exe

-> arg[  6]: -Djava.class.path=E:\usr\sap\SMD\exe\jstartup.jar;E:\usr\sap\SMD\exe\jvmx.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar;..\..\exe\jperflib.jar;lib\patch_7.01.10.1.20110929155938\launcher\smdagentlauncher.jar

-> arg[  7]: -Djava.library.path=C:\j2sdk1.4.2_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\j2sdk1.4.2_17-x64\bin;E:\usr\sap\SMD\exe;C:\Perl\site\bin;C:\Perl\bin;F:\oracle\PNR\11203\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\sysWOW64;C:\PERL\BIN;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\IBM\ITM\bin;C:\IBM\ITM\InstallITM;C:\IBM\ITM\TMAITM6;C:\j2sdk1.4.2_17-x64\bin;F:\oracle\PNR\11203\Opatch;C:\Program Files\IBM\GSK7\bin;C:\Program Files\IBM\GSK7\lib;E:\usr\sap\SMD\exe

-> arg[  8]: -Dmemory.manager=128M

-> arg[  9]: -Xmx128M

-> arg[ 10]: -Xms128M

-> arg[ 11]: -DLoadBalanceRestricted=no

-> arg[ 12]: -Djstartup.mode=JCONTROL

-> arg[ 13]: -Djstartup.ownProcessId=4704

-> arg[ 14]: -Djstartup.ownHardwareId=I0336877146

-> arg[ 15]: -Djstartup.whoami=server

-> arg[ 16]: -Djstartup.debuggable=yes

-> arg[ 17]: -Xss2m

-> arg[ 18]: -DSAPINFO=SMD_98_server

-> arg[ 19]: -DSAPSTARTUP=1

-> arg[ 20]: -DSAPSYSTEM=98

-> arg[ 21]: -DSAPSYSTEMNAME=SMD

-> arg[ 22]: -DSAPMYNAME=ampsv03360prd_SMD_98

-> arg[ 23]: -DSAPDBHOST=

-> arg[ 24]: -Dj2ee.dbhost=

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

[Thr 4784] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [SMDAgent]

-> arg[  0]: run

-> arg[  1]: jcontrol

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

[Thr 4784] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework

[Thr 4784] Sat Sep 28 08:18:05 2013

[Thr 4784] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]

[Thr 4784] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]

[Thr 4784] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]

[Thr 4784] Sat Sep 28 08:18:18 2013

[Thr 4784] JLaunchISetState: change state from [Starting (2)] to [Running (3)]

[Thr 4784] Sat Sep 28 08:18:20 2013

[Thr 4784] JLaunchIStartFunc: end of main method (rc = 0)

[Thr 4920] Sat Sep 28 08:18:21 2013

[Thr 4920] JLaunchIExitJava: exit hook is called (rc = -11112)

[Thr 4920] **********************************************************************

*** 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 4920] JLaunchCloseProgram: good bye (exitcode = -11112)

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
‎11-11-2013 10:18 AM
0 Kudos

Hello S. Sambandam,

Did the Diagnostic Agent run correctly before? If not, check the installation steps in the below note as there were some problems which were discovered after the publication of the installation guide

1144737 - Inst. NW 7.0 SR3/SOLMAN 7.0 - Diagnostics Agent installation

Show replies
Show replies
Former Member
‎11-08-2013 10:15 PM
0 Kudos

-11112 means your aren't connecting to the database. From the information your provided, it seems you haven't identified the database host:

-> arg[ 23]: -DSAPDBHOST=

-> arg[ 24]: -Dj2ee.dbhost=

Show replies
Show replies
Former Member
‎10-24-2013 12:05 PM
0 Kudos

Please attach jvm_SMDAgent.out log file also.

Show replies
Show replies
Reagan
Advisor
Advisor
‎10-24-2013 11:18 AM
0 Kudos

Also try to use SAP JVM

Regards

RB

Show replies
Show replies
Former Member
‎10-24-2013 11:27 AM
0 Kudos

Hi,

Please check the below note,

1927234 - Solution Manager Diagnostics instance fails to start with exitcode = -11112

Thanks

Rishi Abrol

Reagan
Advisor
Advisor
‎10-24-2013 11:15 AM
0 Kudos 
-> arg[  9]: -Xmx128M
-> arg[ 10]: -Xms128M

Increase the heap values to 256 and restart SMD

Regards

RB

Show replies
Show replies
Ask a Question