SMD STOPPED

[Former Member]

Hi people,

I have the next error, the smd instance is stopped, the log file show me

Mar 12, 2009 11:15:31 AM [Thread[main,5,main]] Info Establishing connection to server '[host is empty]' on port

Mar 12, 2009 11:15:31 AM [Thread[main,5,main]] Warning No sld configuration data so SLD Registration is skipped

Mar 12, 2009 11:15:31 AM [Thread[SMDAgent connection thread,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.

What can i do?It´s necessary this instance?

[Former Member]

Hi,

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.

did you try to troubleshoot with above mentioned SAP note in your error message? Please post your results.

hope this helps.

Manoj Chintawar

[Former Member]

Hi

Sometimes even if the SMD agent are running they may not be able to connect to the solution manager or they might be pointing to wrong solution manager.

So always check the log SMDSystem.0.log after the installation of SMD agent.

/usr/sap/SMD/J98/SMDAgent/log

Please attach the logs

Regards

Punit Maini

[Former Member]

In the system landscape there aren´t a solution manager. It´s necessary for his work??

Which log you want?

More thanks

Edited by: Ruben Torres on Mar 12, 2009 3:48 PM

[Former Member]

Hope you might have checked the note 940893 as per above information...

It says....

4. Java VM terminated with a non-zero exit code

These errors require a more detailed analysis.
Therefore, send the complete compressed content of the work directory and the log of
the node affected 
(for example, the content of \usr\sap\SID\inst<No>\j2ee\cluster\server0\log\system\server0.log) t
o SAP Support.

Note for Support employees: See internal Note <999112>.

Helpful Notes:
716604 Access to Sun J2SE and recommended J2SE options
709140 Recommended JDK and VM Settings for the WebAS630/640 SP4
723909 Java VM Settings for J2EE 6.30/6.40/7.0

Could you paste server0.log here as per mentioned...

You can paste only the ERROR part from the log.

I guess it could be VM parameter problem...

just go through note [723909|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=723909] and set the parameters according to your configuration.

Cheers!

[Former Member]

Hi,

No a solution manager is not explicitly needed to get the SMD Agent installed. What is needed is a SLD registration - which you have.

First check whether the configuration of Java VM is according to the sap note:

https://service.sap.com/sap/support/notes/723909

Then try to find whether your error is solved by the following sap note:

https://service.sap.com/sap/support/notes/940893

https://service.sap.com/sap/support/notes/817991

Else, try to re-install the SMD Agent: use the guide -"Diagnostics Agent Setup Guide"

https://websmp107.sap-ag.de/~sapdownload/011000358700000324022008E

- Regards, Dibya

[Former Member]

Hi,

the SMD instance no have the part of JAVA. Then is administrate in the part of the enterprise portal?

More thanks

[Former Member]

Hi people,

Anybody have one "happy" idea?¿?¿

More thanks

[Former Member]

Ruben,

Could you please post values for following parameters?

Xms

Xmx

Also, are you able to logon to SMD http://hostname:50000/smd or http://localhost:50000/smd ?

https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=879377

Hope this helps.

Manoj

[Former Member]

Are the same SMD that SDM??

When i launch Http://hostname:port/smd I get the next message:

404 Not Found SAP J2EE Engine/7.00

The requested resource does not exist.

More thanks

[Former Member]

Hai,

Try patching your SMD according to the patch level of the SMD.

You can get the patches under:

service.sap.com/swdc - Download - SAP Support Packages - Entry by Application Group - SAP Technology Components - Support Packages and Patches - SAP Technology Components - SAP SOLUTION MANAGER - SAP SOLUTION MANAGER 7 - Entry by Component - Solution Manager JAVA Stack - SolManDiag 7.0 - OS independent - LMSERVICE<version>.SCA

Regards,

Yoganand.V

[Former Member]

Thanks,

I can see the diferents patches.I have to import the same level stack that the java part of the enterprise portal?? It´s necessary to have in the systemlandscape the solution manager?

Any idea?

Edited by: Ruben Torres on Mar 24, 2009 9:30 AM

Hi people,

It´s solved. I had to put in the smd.bat, the path of jsdk, and launch the the smdsetup managing config, with the respective parameteres.

More thanks.

Edited by: Ruben Torres on Mar 31, 2009 12:20 PM

[Former Member]

Hello Dibya,

acoordin to note 1144737 we try to apply the command

smdsetup managingconf hostname:"sapms://" what port we must use.

thanks

[Former Member]

Hi,

Could you please post trace file dev_SMDAgent from the work directory?

In the meantime, have a look at following link.

[;

hope this helps.

Manoj

[Former Member]

Thanks for your answer,

Here is the log

-

---

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

-

---

node name : smdagent

pid : 6064

system name : SMD

system nr. : 98

started at : Thu Mar 12 11:47:15 2009

arguments :

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

arg[01] : pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saptest

arg[02] : -DSAPINFO=SMD_98_server

arg[03] : pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saptest

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

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

-> ms host :

-> ms port : 36

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

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Used property files

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

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

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

Instance properties

-> ms host :

-> ms port : 36

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

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Bootstrap nodes

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

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

Worker nodes

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

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

[Thr 8024] Thu Mar 12 11:47:15 2009

[Thr 8024] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 8024] JLaunchRequestQueueInit: create pipe listener thread

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

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

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

[Thr 8024] CPIC (version=700.2006.09.13)

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

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

[Thr 8024] JStartupICheckFrameworkPackage: can't find framework package G:\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 : lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar

-> OS libs path : G:\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 : G:\usr\sap\SMD\exe\jstartup.jar;G:\usr\sap\SMD\exe\jvmx.jar

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

-> parameters : run jcontrol

-> debuggable : yes

-> debug mode : no

-> debug port : 58981

-> shutdown timeout : 20000

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

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

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

[Thr 7700] [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=G:\usr\sap\SMD\SYS\global

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

-> arg[ 6]: -Djava.class.path=G:\usr\sap\SMD\exe\jstartup.jar;G:\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_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\j2sdk1.4.2_17-x64\bin;G:\usr\sap\SMD\exe;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_17-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\;G:\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=6064

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

-> 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=saptest_SMD_98

-> arg[ 23]: -DSAPDBHOST=

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

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

[Thr 7700] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [SMDAgent]

-> arg[ 0]: run

-> arg[ 1]: jcontrol

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

[Thr 7700] Thu Mar 12 11:47:16 2009

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

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

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

[Thr 7700] JLaunchISetState: change state from [Initial (0)] to [Starting (2)]

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

[Thr 6808] **********************************************************************

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

-

---

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

-

---

node name : smdagent

pid : 8936

system name : SMD

system nr. : 98

started at : Thu Mar 12 12:00:15 2009

arguments :

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

arg[01] : pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saptest

arg[02] : -DSAPINFO=SMD_98_server

arg[03] : pf=G:\usr\sap\SMD\J98\..\SYS\profile\SMD_J98_saptest

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

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

-> ms host :

-> ms port : 36

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

-> Admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Used property files

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

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

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

Instance properties

-> ms host :

-> ms port : 36

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

-> admin URL :

-> run mode : NORMAL

-> run action : NONE

-> enabled : yes

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

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

Bootstrap nodes

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

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

Worker nodes

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

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

[Thr 6096] Thu Mar 12 12:00:15 2009

[Thr 6096] JLaunchRequestQueueInit: create named pipe for ipc

[Thr 6096] JLaunchRequestQueueInit: create pipe listener thread

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

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

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

[Thr 6096] CPIC (version=700.2006.09.13)

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

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

[Thr 6096] JStartupICheckFrameworkPackage: can't find framework package G:\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 : lib\launcher\smdagentlauncher.jar;..\..\exe\jstartupapi.jar;..\..\exe\jstartupimpl.jar

-> OS libs path : G:\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 : G:\usr\sap\SMD\exe\jstartup.jar;G:\usr\sap\SMD\exe\jvmx.jar

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

-> parameters : run jcontrol

-> debuggable : yes

-> debug mode : no

-> debug port : 58981

-> shutdown timeout : 20000

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

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

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

[Thr 8112] [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=G:\usr\sap\SMD\SYS\global

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

-> arg[ 6]: -Djava.class.path=G:\usr\sap\SMD\exe\jstartup.jar;G:\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_17-x64\jre\bin\server;C:\j2sdk1.4.2_17-x64\jre\bin;C:\j2sdk1.4.2_17-x64\bin;G:\usr\sap\SMD\exe;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_17-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\;G:\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=8936

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

-> 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=saptest_SMD_98

-> arg[ 23]: -DSAPDBHOST=

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

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

[Thr 8112] JHVM_LoadJavaVM: Java VM created OK.

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

JHVM_BuildArgumentList: main method arguments of node [SMDAgent]

-> arg[ 0]: run

-> arg[ 1]: jcontrol

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

[Thr 8112] Thu Mar 12 12:00:16 2009

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

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

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

[Thr 8112] JLaunchISetState: change state from [Initial (0)] to [Starting (2)]

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

[Thr 2504] **********************************************************************

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