SMDAgent will not start, JVM exitcode = -11112

[Former Member]

Hello,

I'm having problems starting SMDAgent in a NetWeaver 7.0 EHP1 installation. Using SAP Management Console I can verify that its status is always "Starting the processes", but it never turns green.

Doing a deeper analysis inside the Java Process Table node, I see that SMDAgent is stopped. Whenever I try to start it, it gets shut down abnormally. Bellow is the Developer Trace:

trc file: "C:\usr\sap\SMD\J98\work\dev_SMDAgent", trc level: 1, release: "701"
-
node name   : smdagent
pid         : 4956
system name : SMD
system nr.  : 98
started at  : Mon Oct 25 17:24:04 2010
arguments	  :
	  arg[00] : C:\usr\sap\SMD\J98\..\exe\jlaunch.exe
	  arg[01] : pf=C:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_sapmii
	  arg[02] : -DSAPINFO=SMD_98_server
	  arg[03] : pf=C:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_sapmii
**********************************************************************
JStartupReadInstanceProperties: read instance properties [C:\usr\sap\SMD\J98\profile\smd.properties]
-> ms host    : 
-> ms port    : 36
-> OS libs    : C:\usr\sap\SMD\exe
-> Admin URL  : 
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
**********************************************************************
**********************************************************************
Used property files
-> files [00] : C:\usr\sap\SMD\J98\profile\smd.properties
**********************************************************************
**********************************************************************
Instance properties
-> ms host    : 
-> ms port    : 36
-> os libs    : C:\usr\sap\SMD\exe
-> admin URL  : 
-> run mode   : NORMAL
-> run action : NONE
-> enabled    : yes
**********************************************************************
**********************************************************************
Bootstrap nodes
**********************************************************************
**********************************************************************
Worker nodes
-> [00] smdagent             : C:\usr\sap\SMD\J98\profile\smd.properties
**********************************************************************
[Thr 4500] Mon Oct 25 17:24:04 2010
[Thr 4500] JLaunchRequestQueueInit: create named pipe for ipc
[Thr 4500] JLaunchRequestQueueInit: create pipe listener thread
[Thr 2616] JLaunchRequestFunc: Thread 2616 started as listener thread for np messages.
[Thr 1008] WaitSyncSemThread: Thread 1008 started as semaphore monitor thread.
[Thr 4500] NiInit3: NI already initialized; param 'maxHandles' ignored (1;202)
[Thr 4500] CPIC (version=701.2009.01.26)
[Thr 4500] JStartupIReadSection: debug mode is specified by program arguments
[Thr 4500] [Node: SMDAgent] java home is set by profile parameter
	Java Home: C:\j2sdk1.4.2_27-x64
[Thr 4500] JStartupICheckFrameworkPackage: can't find framework package C:\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_27-x64
-> java parameters    : -DP4ClassLoad=P4Connection 
-> java vm version    : 1.4.2_27-b03
-> 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         : lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> OS libs path       : C:\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     : C:\usr\sap\SMD\exe\jstartup.jar;C:\usr\sap\SMD\exe\jvmx.jar
-> shutdown class     : com.sap.smd.agent.launcher.SMDAgentLauncher
-> parameters         : run jcontrol
-> debuggable         : yes
-> debug mode         : yes
-> debug port         : 58981
-> shutdown timeout   : 20000
**********************************************************************
[Thr 4500] JLaunchISetDebugMode: set debug mode [yes]
[Thr 848] JLaunchIStartFunc: Thread 848 started as Java VM thread.
[Thr 848] [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=C:\usr\sap\SMD\SYS\global
-> arg[  5]: -Dapplication.home=C:\usr\sap\SMD\exe
-> arg[  6]: -Djava.class.path=C:\usr\sap\SMD\exe\jstartup.jar;C:\usr\sap\SMD\exe\jvmx.jar;lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar
-> arg[  7]: -Djava.library.path=C:\j2sdk1.4.2_27-x64\jre\bin\server;C:\j2sdk1.4.2_27-x64\jre\bin;C:\j2sdk1.4.2_27-x64\bin;C:\usr\sap\SMD\exe;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_27-x64\bin;C:\Program Files\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\binn\;C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program Files\Microsoft SQL Server\90\DTS\Binn\;C:\usr\sap\SMD\exe
-> arg[  8]: -Xdebug
-> arg[  9]: -Xnoagent
-> arg[ 10]: -Djava.compiler=NONE
-> arg[ 11]: -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=58981
-> arg[ 12]: -Dmemory.manager=128M
-> arg[ 13]: -Xmx128M
-> arg[ 14]: -Xms128M
-> arg[ 15]: -DLoadBalanceRestricted=no
-> arg[ 16]: -Djstartup.mode=JCONTROL
-> arg[ 17]: -Djstartup.ownProcessId=4956
-> arg[ 18]: -Djstartup.ownHardwareId=B0299142182
-> arg[ 19]: -Djstartup.whoami=server
-> arg[ 20]: -Djstartup.debuggable=yes
-> arg[ 21]: -Xss2m
-> arg[ 22]: -DSAPINFO=SMD_98_server
-> arg[ 23]: -DSAPSTARTUP=1
-> arg[ 24]: -DSAPSYSTEM=98
-> arg[ 25]: -DSAPSYSTEMNAME=SMD
-> arg[ 26]: -DSAPMYNAME=sapmii_SMD_98
-> arg[ 27]: -DSAPDBHOST=
-> arg[ 28]: -Dj2ee.dbhost=
**********************************************************************
[Thr 848] JHVM_LoadJavaVM: Java VM created OK.
**********************************************************************
JHVM_BuildArgumentList: main method arguments of node [SMDAgent]
-> arg[  0]: run
-> arg[  1]: jcontrol
**********************************************************************
[Thr 848] JHVM_RegisterNatives: registering methods in com.sap.bc.proj.jstartup.JStartupFramework
[Thr 848] Mon Oct 25 17:24:05 2010
[Thr 848] JLaunchISetState: change state from [Initial (0)] to [Initial (0)]
[Thr 848] JLaunchISetState: change state from [Initial (0)] to [Waiting for start (1)]
[Thr 848] JLaunchISetState: change state from [Waiting for start (1)] to [Starting (2)]
[Thr 848] JLaunchIStartFunc: end of main method (rc = 0)
[Thr 1580] Mon Oct 25 17:24:06 2010
[Thr 1580] JLaunchIExitJava: exit hook is called (rc = -11112)
[Thr 1580] **********************************************************************
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 1580] JLaunchCloseProgram: good bye (exitcode = -11112)

What is the meaning of error code -11112?

Regards,

David

[Former Member · Accepted solution]

Hi,

Pls check the java environmental variables and increase the Virtual memory.

Regards,

Phani

[TomCenens · Accepted solution]

Dear

Please read SAP note [https://service.sap.com/sap/support/notes/940893] and follow the instructions to find the root cause for the issue.

You can also check the SMD Agent troubleshooting PDF guide which has case per case issues and solutions, I believe the existcode you are experiencing is also mentioned in this guide:

[http://www.scribd.com/doc/35711448/DiagAgent-Troubleshooting]

Kind regards

Tom

[Former Member · Accepted solution]

Hello,

following the guide mentioned by Tom, I found out that exitcode = -11112 is related to an authentication problem. Since all authentication problems are logged in file SMDSystem.log, here is the output of our system:

Nov 17, 2010 10:31:01 AM [Thread[main,5,main]] Info       Starting SMDAgent ...
Nov 17, 2010 10:31:01 AM [Thread[main,5,main]] Info       ===> Establishing connection to server '[host is empty]' on port [port is empty]
Nov 17, 2010 10:31:01 AM [Thread[main,5,main]] Warning    [SLDConfigurationLoader] No sld configuration data so SLD Registration is skipped
Nov 17, 2010 10:31:01 AM [Thread[Connector,5,main]] Fatal      Cannot find sld guid to register the agent in passive mode and no credentials of managing system. The Agent will be stop because SLD configuration doesn't exist.
Nov 17, 2010 10:31:01 AM [Thread[main,5,main]] Error      Exception occured when in smd agent waiting thread. 
[EXCEPTION]
 java.lang.IllegalStateException: Shutdown in progress
	at java.lang.Shutdown.add(Shutdown.java:79)
	at java.lang.Runtime.addShutdownHook(Runtime.java:190)
	at com.sap.smd.agent.SMDAgent.awaitTermination(SMDAgent.java:266)
	at com.sap.smd.agent.SMDAgent.run(SMDAgent.java:202)
	at com.sap.smd.agent.launcher.SMDAgentLauncher.launchAgent(SMDAgentLauncher.java:194)
	at com.sap.smd.agent.launcher.SMDAgentLauncher.main(SMDAgentLauncher.java:69)

This means that I need to configure the connection to my Solution Manager right? How can I do that? If that connection is not possible, in case there is a network problem or something like that, how should I proceed?

Best Regards,

David

[TomCenens · Accepted solution]

Hello David

I would advise you to register the agents in a central existing SLD which is recommended by SAP.

I always register the agents in the SLD of the SAP Solution Manager (but depending on your landscape your SLD can reside elsewhere, just make sure the SAP Solution Manager is connected to it to recognize the agents afterwards).

You can still alter the configuration afterwards using the smdsetup.sh script in the scripts folder (in your agent installation folder/filesystem) but filling in the screens in SAPinst is easier really as SAPinst also validates the input and makes a connection so you are sure it's done properly.

You can run smdsetup.sh without any additional parameters to get the list of possibile parameters that you can use with the script to perform those actions.

If you think it's too much hassle, a fast and easy way is reinstalling the SMD agent, the SAPinst procedure does not take long.

If the connection is not available, your agent will not do anything, as it's purpose is collect data from your managed SAP system and send it to the managing SAP system (which is normally Solution Manager).

It sounds like this is the first agent you install, I would strongly recommend to use a seperate SID (if not yet the case) also and not use /usr/sap/SMD as that is recommended by SAP to use unique SID for SMD Agent 7.11.

Another point to avoid issues afterwards is that it is best that you download the latest SAPJVM package for your OS and browse it in SAPinst where you can choose an alternate version than the one from the standalone DVD (or other DVD which you are using to install). Older SAPJVM version can give issues with certain path determination through your folders/filesystems.

Kind regards

Tom

[fjhernanz]

Hi,

Do you have any othe additional error on jvm_SMDAgent.out ?

Br,

Javier