- SAP Community
- Products and Technology
- Technology
- Technology Q&A
- SMD agent gets offline after some minutes
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
SMD agent gets offline after some minutes
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 09-10-2015 12:37 PM
Hi, I have seen several cases like mine here, but somehow the provided answers don't fit.
We have several SMD agents installed, some of them as local agents on windows machines for EEM.
But one agent on my local PC is always disconnecting since some time. I can't exactly tell, when this started. I know that it worked last December, but fails at least since end of August, 2015.
Symptom:
in dev_smdagent:
J Thu Sep 10 13:01:38 2015
J : [12624] 13:01:38 ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264
F
F [Thr 764] Thu Sep 10 13:01:46 2015
F [Thr 764] *** LOG => State changed from 3 (Running) to 10 (Starting apps).
F [Thr 764] *** LOG state real time: 240.286 CPU time: 0.405 sys, 3.088 usr
F [Thr 764] *** LOG total real time: 10655.463 CPU time: 67.096 sys, 270.037 usr
F [Thr 764]
F
F [Thr 764] Thu Sep 10 13:01:54 2015
F [Thr 764] *** LOG => State changed from 10 (Starting apps) to 3 (Running).
F [Thr 764] *** LOG state real time: 8.281 CPU time: 0.826 sys, 2.948 usr
F [Thr 764] *** LOG total real time: 10663.744 CPU time: 67.922 sys, 272.986 usr
F [Thr 764]
this is repeating every five minutes or so.
Corresponding error message in the Agent-Errorlog on the Solman:
| Sep 10, 2015 12:53:17 PM | SMDloggerSystem | [ms://r0184i1:8101/P4] Ping failed (java.rmi.RemoteException) com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of C011A0170.group.rwe.com_DAA_SMDA98. |
This is the SMDSystem.log:
| Sep 10, 2015 1:02:46 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideD...] Info | Reading JStartup environment... | |
| Sep 10, 2015 1:02:46 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideD...] Info | 'SAPLOCALHOST' found, The value 'C011A0170' will be used to determine the Agent name. | |
| Sep 10, 2015 1:02:46 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideD...] Info | InetAddress Resolving for 'C011A0170' - FQN: C011A0170.group.rwe.com SQN: C011A0170 IP: 10.183.81.13 | |
| Sep 10, 2015 1:02:46 PM [Thread[ExRun:OutsideDiscovery_1,5,OutsideD...] Info | InetAddress Resolving for localhost - FQN: C011A0170.group.rwe.com SQN: C011A0170 IP: 10.183.81.13 | |
| Sep 10, 2015 1:05:17 PM [Thread[Connector,5,main] | ] Error | [ms://r0184i1:8101/P4] Ping failed (java.rmi.RemoteException) java.rmi.RemoteException: Agent not known on server. |
| Sep 10, 2015 1:05:17 PM [Thread[ExRun:default_1,5,default:ExecTG] | ] Info | [J2EEClusterConnector.forgetAccessPoint] Connection status changed to DISCONNECTED. Forgotting all access points. |
| Sep 10, 2015 1:05:17 PM [Thread[Connector,5,main] | ] Info | [SMDConnector.resetBroker] reset the p4 broker (close:true) |
| Sep 10, 2015 1:05:17 PM [Thread[Connector,5,main] | ] Info | [SMDConnector.resetBroker] p4 broker closed. |
And this is from the smdagent_trace file:
#1.5 #020085E2EC040001000006EE00001D5400051F6293326155#1441883120815#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###Old Agent Handle com.sap.smd.agent.AgentHandle@5b1e96 cleanup.#
#1.5 #020085E2EC040001000006EF00001D5400051F629332B139#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###Reading JStartup environment...#
#1.5 #020085E2EC040001000006F000001D5400051F629332B1A0#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###'SAPLOCALHOST' found, The value 'C011A0170' will be used to determine the Agent name.#
#1.5 #020085E2EC040001000006F100001D5400051F629332B208#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###InetAddress Resolving for 'C011A0170' - FQN: C011A0170.group.rwe.com SQN: C011A0170 IP: 10.183.81.13#
#1.5 #020085E2EC040001000006F200001D5400051F629332B330#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###InetAddress Resolving for localhost - FQN: C011A0170.group.rwe.com SQN: C011A0170 IP: 10.183.81.13#
#1.5 #020085E2EC040001000006F300001D5400051F629332B3C4#1441883120836#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###Agent Handle have been created#
#1.5 #020085E2EC040001000006F400001D5400051F629332B4A0#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain### Agent Version .............. : 7.10.12.2.20141128090136#
#1.5 #020085E2EC040001000006F500001D5400051F629332B4F5#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain### Agent ID ................... : C011A0170.group.rwe.com_DAA_SMDA98#
#1.5 #020085E2EC040001000006F600001D5400051F629332B53E#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain### Assigned Server Name ....... : rob_r002358#
#1.5 #020085E2EC040001000006F700001D5400051F629332B58B#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain### Canonical Host Name ........ : C011A0170.group.rwe.com#
#1.5 #020085E2EC040001000006F800001D5400051F629332B5CD#1441883120837#SMDloggerSystem##SMDloggerSystem#######Thread[Connector,5,main]##0#0#Info##Plain###[ms://r0184i1:8101/P4] Registering agent on server ... #
#1.5 #020085E2EC0400E40000000000001D5400051F6293474752#1441883122185#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[AgentContext.stopApplications] Stopping Agent applications ...#
#1.5 #020085E2EC0400E40000000100001D5400051F6293474F02#1441883122187#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{selfd:filter}.#
#1.5 #020085E2EC0400E40000000200001D5400051F62934751CF#1441883122188#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###Cannot close the thread group selfd:filter#
#1.5 #020085E2EC0400E40000000300001D5400051F629356FDEA#1441883123214#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{e2emai:jobmgr}.#
#1.5 #020085E2EC0400E40000000400001D5400051F6293570E9F#1441883123219#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@2c8d79 (entities:com.sap.smd.agent.application.e2emai.MAIService [ref])]: unload did not unregister all dependencies of entities:com.sap.smd.agent.application.e2emai.MAIService#
#1.5 #020085E2EC0400E40000000500001D5400051F6293570F7F#1441883123219#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@1cb215e (states:dpc.startup [ref])]: unload did not unregister dependant "entities:com.sap.smd.agent.application.e2emai.MAIService" of "states:dpc.startup" - could be cycle. Will clean dependants set now!#
#1.5 #020085E2EC0400E40000000600001D5400051F6293582B0F#1441883123292#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{dpc:job}.#
#1.5 #020085E2EC0400E40000000700001D5400051F6293583E69#1441883123297#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group dpc:job is already closed.#
#1.5 #020085E2EC0400E40000000800001D5400051F6293583F03#1441883123297#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group dpc:job is already closed.#
#1.5 #020085E2EC0400E40000000900001D5400051F62935842C5#1441883123298#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{check}.#
#1.5 #020085E2EC0400E40000000A00001D5400051F6293585A3B#1441883123304#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group check is already closed.#
#1.5 #020085E2EC0400E40000000B00001D5400051F6293585AD1#1441883123304#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group check is already closed.#
#1.5 #020085E2EC0400E40000000C00001D5400051F6293586C0B#1441883123308#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{agelet_WilyEM}.#
#1.5 #020085E2EC0400E40000000D00001D5400051F629358713E#1441883123310#com.sap.smd.e2edcc##com.sap.smd.e2edcc#######Thread[Thread-628,5,main]##0#0#Info##Plain###[DCCService.clean] DCCService cleaned.#
#1.5 #020085E2EC0400E40000000E00001D5400051F62935871CE#1441883123310#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{OutsideDiscovery}.#
#1.5 #020085E2EC0400E40000000F00001D5400051F62935874E5#1441883123311#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group OutsideDiscovery is already closed.#
#1.5 #020085E2EC0400E40000001000001D5400051F629358751F#1441883123311#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group OutsideDiscovery is already closed.#
#1.5 #020085E2EC0400E40000001100001D5400051F629358758B#1441883123311#com.sap.smd.e2edcc##com.sap.smd.e2edcc#######Thread[Thread-628,5,main]##0#0#Info##Plain###[DCCService.dispose] DCCService released.#
#1.5 #020085E2EC0400E40000001200001D5400051F6293587661#1441883123311#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[WHS] Shutting down Wily Handler Service#
#1.5 #020085E2EC0400E40000001300001D5400051F62935883ED#1441883123314#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@14d1e30 (applications:com.sap.smd.agent.application.e2emai [ref])]: trying to unload dependent "entities:com.sap.smd.agent.application.e2emai.MAIService" revealed dependency to non-existent broker#
#1.5 #020085E2EC0400E40000001400001D5400051F6293588587#1441883123315#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@c11070 (applications:com.sap.smd.agent.application.nodescontroller [ref])]: trying to unload dependent "entities:com.sap.smd.agent.application.nodescontroller.nodesController" revealed dependency to non-existent broker#
#1.5 #020085E2EC0400E40000001500001D5400051F6293588821#1441883123316#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Warning##Plain###[com.sap.smd.om.impl.broker.ObjectReference@13853f7 (applications:com.sap.smd.agent.application.runtime [ref])]: trying to unload dependent "entities:com.sap.smd.agent.application.runtime.servicesEntityFactory" revealed dependency to non-existent broker#
#1.5 #020085E2EC0400E40000001600001D5400051F629358893A#1441883123316#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{WILYHOST_SCHEDULER}.#
#1.5 #020085E2EC0400E40000001700001D5400051F6293588CF6#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group WILYHOST_SCHEDULER is already closed.#
#1.5 #020085E2EC0400E40000001800001D5400051F6293588D5E#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group WILYHOST_SCHEDULER is already closed.#
#1.5 #020085E2EC0400E40000001900001D5400051F6293588DA3#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{EEM_SCHEDULER}.#
#1.5 #020085E2EC0400E40000001A00001D5400051F6293588F4B#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the deamon thread group EEM_SCHEDULER is already closed.#
#1.5 #020085E2EC0400E40000001B00001D5400051F6293588FA1#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###the thread group EEM_SCHEDULER is already closed.#
#1.5 #020085E2EC0400E40000001C00001D5400051F6293588FDF#1441883123317#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{com.sap.maimgr}.#
#1.5 #020085E2EC0400E40000001D00001D5400051F6293589086#1441883123318#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[ExecutionManager.Shutdown] Shutting down ExecutionManager{com.sap.exmmgr}.#
#1.5 #020085E2EC0400E40000001E00001D5400051F62935890D5#1441883123318#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[AgentContext.stopApplications] Agent Applications stopped.#
#1.5 #020085E2EC0400E40000001F00001D5400051F62938A1C1E#1441883126564#SMDloggerSystem##SMDloggerSystem#######Thread[Thread-628,5,main]##0#0#Info##Plain###[AgentContext.startApplications] Starting Agent Applications...#
And what I did: I re-registerd the SMD agent with
smdsetup managingconf hostname:"sapms://r0184i1.rwe.com" port:"8101" user:"*******" pwd:"*****"
several times (without error), restarted the SAP hostagent and the SMD agent, but every five minutes or so the agent restarts and disappears from the list of available agents.
Connection method for all robot pc agents is MS/P4, since our solution manager is clustered. All agents are 32bit, Version 7.10.12.2
Any suggestions?
thanks for your advice in advance ...
- SAP Managed Tags:
- SAP Solution Manager
Accepted Solutions (1)
Accepted Solutions (1)
daniel_nicol
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
From the logs I believe it could be the issue described in note 2183337. Please check if the patch level of the LM-Service is at least on the level in which this issue is corrected, otherwise you may have to implement a new patch level. Make sure that only a patch level is implemented, and not a support package.
Best regards,
Daniel.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Answers (8)
Answers (8)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi everybody,
In the end Daniel was right, and we had to patch LM-Service.
But the patchlevel from note 2183337 has other bugs, so don't use this but take the next one (for 7.10 SP 12 this would be P06 instead of P05 as mentionend in note 2183337).
Regards
Ralf
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Ralf,
have you found a solution for the problem?
Best Regards,
Blacky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
we have now ta similar problem,
did someone know the soltion for these problem?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
dev_jstart (only last minutes)
F [Thr 3544] Fri Sep 25 05:14:51 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:17:07 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:18:24 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:22:12 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:26:29 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:30:18 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:34:36 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:38:25 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:42:15 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:46:33 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:50:21 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:54:38 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:58:26 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 05:59:13 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:02:31 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:06:18 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:10:36 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:14:24 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:15:13 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:18:29 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:22:17 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:26:35 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:30:24 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:34:13 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:37:59 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:42:20 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:46:06 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:49:53 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:54:12 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
F
F [Thr 3544] Fri Sep 25 06:58:11 2015
F [Thr 3544] *** WARNING => SfCJavaProcHandler(smdagent)::doProcState: unexpected 1040 RUNNING in state 1040 RUNNING! [sfxxproc.hpp 1105]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
dev_sdmagent (only last minutest).
J Fri Sep 25 06:37:38 2015
J : [5844] 06:37:38 ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264
F
F [Thr 6520] Fri Sep 25 06:37:54 2015
F [Thr 6520] *** LOG => State changed from 3 (Running) to 10 (Starting apps).
F [Thr 6520] *** LOG state real time: 220.839 CPU time: 2.262 sys, 4.134 usr
F [Thr 6520] *** LOG total real time: 59414.937 CPU time: 760.536 sys, 2078.806 usr
F [Thr 6520]
F
F [Thr 6520] Fri Sep 25 06:37:59 2015
F [Thr 6520] *** LOG => State changed from 10 (Starting apps) to 3 (Running).
F [Thr 6520] *** LOG state real time: 4.635 CPU time: 1.419 sys, 3.494 usr
F [Thr 6520] *** LOG total real time: 59419.572 CPU time: 761.955 sys, 2082.301 usr
F [Thr 6520]
J
J Fri Sep 25 06:41:56 2015
J : [5844] 06:41:56 ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264
F
F [Thr 12460] Fri Sep 25 06:42:13 2015
F [Thr 12460] *** LOG => State changed from 3 (Running) to 10 (Starting apps).
F [Thr 12460] *** LOG state real time: 253.978 CPU time: 2.184 sys, 5.116 usr
F [Thr 12460] *** LOG total real time: 59673.551 CPU time: 764.139 sys, 2087.418 usr
F [Thr 12460]
F
F [Thr 12460] Fri Sep 25 06:42:20 2015
F [Thr 12460] *** LOG => State changed from 10 (Starting apps) to 3 (Running).
F [Thr 12460] *** LOG state real time: 6.845 CPU time: 1.310 sys, 3.510 usr
F [Thr 12460] *** LOG total real time: 59680.396 CPU time: 765.450 sys, 2090.928 usr
F [Thr 12460]
J
J Fri Sep 25 06:45:44 2015
J : [5844] 06:45:44 ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264
F
F [Thr 5080] Fri Sep 25 06:46:01 2015
F [Thr 5080] *** LOG => State changed from 3 (Running) to 10 (Starting apps).
F [Thr 5080] *** LOG state real time: 220.856 CPU time: 2.074 sys, 3.993 usr
F [Thr 5080] *** LOG total real time: 59901.253 CPU time: 767.524 sys, 2094.921 usr
F [Thr 5080]
F
F [Thr 5080] Fri Sep 25 06:46:06 2015
F [Thr 5080] *** LOG => State changed from 10 (Starting apps) to 3 (Running).
F [Thr 5080] *** LOG state real time: 5.140 CPU time: 1.310 sys, 3.712 usr
F [Thr 5080] *** LOG total real time: 59906.393 CPU time: 768.835 sys, 2098.634 usr
F [Thr 5080]
J
J Fri Sep 25 06:49:32 2015
J : [5844] 06:49:32 ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264
F
F [Thr 14436] Fri Sep 25 06:49:49 2015
F [Thr 14436] *** LOG => State changed from 3 (Running) to 10 (Starting apps).
F [Thr 14436] *** LOG state real time: 222.873 CPU time: 2.324 sys, 4.118 usr
F [Thr 14436] *** LOG total real time: 60129.266 CPU time: 771.159 sys, 2102.753 usr
F [Thr 14436]
F
F [Thr 14436] Fri Sep 25 06:49:53 2015
F [Thr 14436] *** LOG => State changed from 10 (Starting apps) to 3 (Running).
F [Thr 14436] *** LOG state real time: 4.730 CPU time: 1.310 sys, 3.619 usr
F [Thr 14436] *** LOG total real time: 60133.996 CPU time: 772.470 sys, 2106.372 usr
F [Thr 14436]
J
J Fri Sep 25 06:53:50 2015
J : [5844] 06:53:50 ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264
F
F [Thr 13956] Fri Sep 25 06:54:06 2015
F [Thr 13956] *** LOG => State changed from 3 (Running) to 10 (Starting apps).
F [Thr 13956] *** LOG state real time: 253.039 CPU time: 2.230 sys, 4.633 usr
F [Thr 13956] *** LOG total real time: 60387.035 CPU time: 774.700 sys, 2111.005 usr
F [Thr 13956]
F
F [Thr 13956] Fri Sep 25 06:54:12 2015
F [Thr 13956] *** LOG => State changed from 10 (Starting apps) to 3 (Running).
F [Thr 13956] *** LOG state real time: 5.301 CPU time: 1.045 sys, 3.853 usr
F [Thr 13956] *** LOG total real time: 60392.337 CPU time: 775.746 sys, 2114.858 usr
F [Thr 13956]
J
J Fri Sep 25 06:57:37 2015
J : [5844] 06:57:37 ***Warning: Thread.stop(): Thread.stop() called using java.lang.ThreadDeath in com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.close()V:264
F
F [Thr 15980] Fri Sep 25 06:57:55 2015
F [Thr 15980] *** LOG => State changed from 3 (Running) to 10 (Starting apps).
F [Thr 15980] *** LOG state real time: 223.054 CPU time: 2.121 sys, 4.180 usr
F [Thr 15980] *** LOG total real time: 60615.391 CPU time: 777.867 sys, 2119.039 usr
F [Thr 15980]
F
F [Thr 15980] Fri Sep 25 06:58:11 2015
F [Thr 15980] *** LOG => State changed from 10 (Starting apps) to 3 (Running).
F [Thr 15980] *** LOG state real time: 16.046 CPU time: 1.404 sys, 3.759 usr
F [Thr 15980] *** LOG total real time: 60631.438 CPU time: 779.271 sys, 2122.799 usr
F [Thr 15980]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
jvm_sdmagent.out:
AgentLauncherLogger [debug]: run
AgentLauncherLogger [debug]: ***********************************************************************
AgentLauncherLogger [debug]: * LoadBalanceRestricted=false
AgentLauncherLogger [debug]: * P4ClassLoad=P4Connection
AgentLauncherLogger [debug]: * SAPDBHOST=
AgentLauncherLogger [debug]: * SAPINFO=DAA_98_smdagent
AgentLauncherLogger [debug]: * SAPJStartVersion=721, patch 201, changelist 1459980, NTintel, optU (Dec 4 2013, 16:50:29)
AgentLauncherLogger [debug]: * SAPMYNAME=C011A0170_DAA_98
AgentLauncherLogger [debug]: * SAPSTARTUP=1
AgentLauncherLogger [debug]: * SAPSYSTEM=98
AgentLauncherLogger [debug]: * SAPSYSTEMNAME=DAA
AgentLauncherLogger [debug]: * application.home=C:\usr\sap\DAA\SMDA98\exe
AgentLauncherLogger [debug]: * awt.toolkit=sun.awt.windows.WToolkit
AgentLauncherLogger [debug]: * com.sap.vm.codeline=61_REL
AgentLauncherLogger [debug]: * com.sap.vm.compressedoops=false
AgentLauncherLogger [debug]: * com.sap.vm.profilingserver=true
AgentLauncherLogger [debug]: * com.sap.vm.type=opt
AgentLauncherLogger [debug]: * com.sap.vm.version=10
AgentLauncherLogger [debug]: * env.class.path=
AgentLauncherLogger [debug]: * file.encoding=Cp1252
AgentLauncherLogger [debug]: * file.encoding.pkg=sun.io
AgentLauncherLogger [debug]: * file.separator=\
AgentLauncherLogger [debug]: * j2ee.dbhost=
AgentLauncherLogger [debug]: * java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment
AgentLauncherLogger [debug]: * java.awt.printerjob=sun.awt.windows.WPrinterJob
AgentLauncherLogger [debug]: * java.class.path=C:\usr\sap\DAA\SMDA98\exe\jstart71.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\DAA\SMDA98\exe\jre\lib\iqlib.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\tools.jar;lib\iaik\iaik_jce.jar;lib\iaik\iaik_jsse.jar;lib\iaik\iaik_smime.jar;lib\iaik\iaik_ssl.jar;lib\iaik\w3c_http.jar;..\exe\jstartupapi.jar;..\exe\jstartupimpl.jar;..\exe\jperflib.jar;lib\patch_7.10.12.2.20141128091431\launcher\smdagentlauncher.jar
AgentLauncherLogger [debug]: * java.class.version=50.0
AgentLauncherLogger [debug]: * java.endorsed.dirs=C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\endorsed
AgentLauncherLogger [debug]: * java.ext.dirs=C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\ext-sap;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
AgentLauncherLogger [debug]: * java.home=C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre
AgentLauncherLogger [debug]: * java.io.tmpdir=C:\usr\sap\DAA\tmp\
AgentLauncherLogger [debug]: * java.library.path=C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\bin\server;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\bin;C:\usr\sap\DAA\SMDA98\j2ee\os_libs;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\bin;C:\usr\sap\DAA\SMDA98\exe;C:\Program Files\Common Files\Microsoft Shared\Microsoft Online Services;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft Application Virtualization Client;c:\Program Files\WIDCOMM\Bluetooth Software;C:\Program Files\Hewlett-Packard\HP ProtectTools Security Manager\Bin;C:\Program Files\Hummingbird\Connectivity\14.00\Accessories;C:\Program Files\Hummingbird\Connectivity\14.00\NFS Maestro;C:\usr\sap\DAA\SYS\exe\uc\NTI386
AgentLauncherLogger [debug]: * java.runtime.name=Java(TM) SE Runtime Environment
AgentLauncherLogger [debug]: * java.runtime.version=6.1.064
AgentLauncherLogger [debug]: * java.specification.name=Java Platform API Specification
AgentLauncherLogger [debug]: * java.specification.vendor=Sun Microsystems Inc.
AgentLauncherLogger [debug]: * java.specification.version=1.6
AgentLauncherLogger [debug]: * java.vendor=SAP AG
AgentLauncherLogger [debug]: * java.vendor.url=http://www.sap.com/
AgentLauncherLogger [debug]: * java.vendor.url.bug=http://service.sap.com/support
AgentLauncherLogger [debug]: * java.version=1.6.0_71
AgentLauncherLogger [debug]: * java.vm.info=Mar 14 2014 00:50:24 - 61_REL - optU - windows x86 - 6 - bas2:213865 (mixed mode)
AgentLauncherLogger [debug]: * java.vm.name=SAP Java Server VM
AgentLauncherLogger [debug]: * java.vm.specification.name=Java Virtual Machine Specification
AgentLauncherLogger [debug]: * java.vm.specification.vendor=Sun Microsystems Inc.
AgentLauncherLogger [debug]: * java.vm.specification.version=1.0
AgentLauncherLogger [debug]: * java.vm.vendor=SAP AG
AgentLauncherLogger [debug]: * java.vm.version=6.1.064 24.51-b11
AgentLauncherLogger [debug]: * jstartup.debuggable=yes
AgentLauncherLogger [debug]: * jstartup.mode=JSTART
AgentLauncherLogger [debug]: * jstartup.ownHardwareId=B0595593415
AgentLauncherLogger [debug]: * jstartup.ownProcessId=3484
AgentLauncherLogger [debug]: * jstartup.whoami=java
AgentLauncherLogger [debug]: * line.separator=
AgentLauncherLogger [debug]: * os.arch=x86
AgentLauncherLogger [debug]: * os.name=Windows 7
AgentLauncherLogger [debug]: * os.version=6.1
AgentLauncherLogger [debug]: * path.separator=;
AgentLauncherLogger [debug]: * sun.arch.data.model=32
AgentLauncherLogger [debug]: * sun.boot.class.path=C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\sapjvm-alt-rt.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\resources.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\rt.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\sunrsasign.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\jsse.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\jce.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\charsets.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\lib\jfr.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\classes
AgentLauncherLogger [debug]: * sun.boot.library.path=C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre\bin
AgentLauncherLogger [debug]: * sun.cpu.endian=little
AgentLauncherLogger [debug]: * sun.cpu.isalist=pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86
AgentLauncherLogger [debug]: * sun.desktop=windows
AgentLauncherLogger [debug]: * sun.io.unicode.encoding=UnicodeLittle
AgentLauncherLogger [debug]: * sun.java.launcher=jstart
AgentLauncherLogger [debug]: * sun.jnu.encoding=Cp1252
AgentLauncherLogger [debug]: * sun.management.compiler=HotSpot Tiered Compilers
AgentLauncherLogger [debug]: * sun.os.patch.level=Service Pack 1
AgentLauncherLogger [debug]: * sys.global.dir=C:\usr\sap\DAA\SYS\global
AgentLauncherLogger [debug]: * user.country=DE
AgentLauncherLogger [debug]: * user.dir=C:\usr\sap\DAA\SMDA98\SMDAgent
AgentLauncherLogger [debug]: * user.home=C:\Users\SAPServiceDAA
AgentLauncherLogger [debug]: * user.language=de
AgentLauncherLogger [debug]: * user.name=SAPServiceDAA
AgentLauncherLogger [debug]: * user.timezone=
AgentLauncherLogger [debug]: * user.variant=
AgentLauncherLogger [debug]: ***********************************************************************
AgentLauncherLogger [info]: Running SMD Agent ...
adding Provider IAIK...
Java version number: 1.6.0_71
Java compiler: null
Java vendor-specific string: SAP AG
Java vendor URL: http://www.sap.com/
Java installation directory: C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\jre
Java class format version number: 50.0
Java class path: C:\usr\sap\DAA\SMDA98\exe\jstart71.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\jvmx.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\jvmx_tools.jar;C:\usr\sap\DAA\SMDA98\exe\jre\lib\iqlib.jar;C:\usr\sap\DAA\SMDA98\exe\sapjvm_6\lib\tools.jar;lib\iaik\iaik_jce.jar;lib\iaik\iaik_jsse.jar;lib\iaik\iaik_smime.jar;lib\iaik\iaik_ssl.jar;lib\iaik\w3c_http.jar;..\exe\jstartupapi.jar;..\exe\jstartupimpl.jar;..\exe\jperflib.jar;lib\patch_7.10.12.2.20141128091431\launcher\smdagentlauncher.jar
Operating system name: Windows 7
Operating system architecture: x86
Operating system version: 6.1
Installed security providers providers:
Provider 1: IAIK version: 3.1810000000000005
Provider 2: SUN version: 1.6
Provider 3: SunRsaSign version: 1.5
Provider 4: SunJSSE version: 1.6
Provider 5: SunJCE version: 1.6
Provider 6: SunJGSS version: 1.0
Provider 7: SunSASL version: 1.5
Provider 8: XMLDSig version: 1.0
Provider 9: SunPCSC version: 1.6
Provider 10: SunMSCAPI version: 1.6
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Introscope Agent Release 8.2.4.0 (Build 476771)
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Using Java VM version "SAP Java Server VM 1.6.0_71" from SAP AG
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Trying to load agent profile based on system property "com.wily.introscope.agentProfile"
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Trying to load file from C:\usr\sap\DAA\SMDA98\SMDAgent\applications.config\com.sap.smd.agent.application.wilyhost\ActiveIntroscopeSapAgent.profile
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Loaded file from C:\usr\sap\DAA\SMDA98\SMDAgent\applications.config\com.sap.smd.agent.application.wilyhost\ActiveIntroscopeSapAgent.profile
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Agent Metric Aging is turned off
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.heartbeatInterval is set to 1800
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.dataChunk is set to 500
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Agent Metric Aging: property introscope.agent.metricAging.numberTimeslices is set to 3000
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Looking for agent profile property "introscope.agent.extensions.directory" to locate the extensions directory.
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] The agent extensions directory C:\usr\sap\DAA\SMDA98\SMDAgent\applications.config\com.sap.smd.agent.application.wilyhost\ext was successfully located
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Introscope Agent startup complete.
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] The Agent will attempt to determine its name.
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Using the Agent name "SAP HostAgent SMDA98" based on the value of the System Property "com.wily.introscope.agent.agentName".
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Initial agent name set to SAP HostAgent SMDA98
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent.Isengard] Initiating connection attempts to the Introscope Enterprise Manager.
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Started Error Reporting service
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent.Isengard] The Agent reconnection delay is set to 15 second(s).
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] Waiting for the agent server connection to set the sampling per interval and samples per intervals
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent.IsengardServerConnectionManager] Connected Agent to the Introscope Enterprise Manager at s060l0096.rwe.com:6001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory. Host = "rob_r002358", Process = "SAP HostAgent Process", Agent Name = "SAP HostAgent SMDA98".
9/24/15 02:08:31 PM CEST [INFO] [IntroscopeAgent] add filters called
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Ralf,
logs which you posted indicates issue with Wily Introscope.
Can you please use EM Perflog Analyzer to make sure that your Wily Introscope is able to handle workload?
How to use EM Perflog Analyzer you can find:
EM Perflog Analyzer Tool - Technical Operations - SCN Wiki
Thanks
Monika
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Check SMD Agent application log. it could be a VM issue. We had this problem with our RHEL Linux environment. To address it, we reinstalled HOSTAGENT and then restarted SMD AGENT.
As a rule, whenever restarting SMD AGENT Also ensure that HOSTAGENT is rebooted. SMD AGENT need HOSTAGENT program saphostexe to be running.
If still an issue, let me know.
Thanks
ABhijeet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi Abhijeet,
thank you for your reply. However I'm not convinced that this is a jvm error.
The SMDAgentApplicationLog is just full of stuffl ike this:
| Sep 21, 2015 7:38:16 AM [Thread[EEM/EP5510A_Debitor aendern Neuss 4...] Warning | com.sap.smd.wily.hostagent.metric.MetricArea - createDataAccumulator: for metric SelfMonitoring|Action|EEM/EP5510A_Debitor aendern Neuss 4026993/1:Average Response Time (ms): com.wily.introscope.agent.stat.AccumulatorAlreadyExistsException: Agent_Accumulator_Already_Exists_Message[Average Response Time (ms)] |
| Sep 21, 2015 7:38:16 AM [Thread[ExRun:WILYHOST_SCHEDULER_21,5,WILYH...] Error | com.sap.smd.wily.hostagent.action.AbstractAction - doOffset: |
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.smd.wily.hostagent.action.AbstractAction.doStartTimeAndOffset(AbstractAction.java:246)
at com.sap.smd.eem.agelet.EEMAction.doStartTimeAndOffset(EEMAction.java:133)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:75)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
| Sep 21, 2015 7:38:16 AM [Thread[EEM/EP5510A_Debitor aendern Nordhor...] Warning | com.sap.smd.wily.hostagent.metric.MetricArea - createDataAccumulator: for metric SelfMonitoring|Action|EEM/EP5510A_Debitor aendern Nordhorn 4026992/1:Average Response Time (ms): com.wily.introscope.agent.stat.AccumulatorAlreadyExistsException: Agent_Accumulator_Already_Exists_Message[Average Response Time (ms)] |
| Sep 21, 2015 7:38:16 AM [Thread[ExRun:WILYHOST_SCHEDULER_11,5,WILYH...] Error | com.sap.smd.wily.hostagent.action.AbstractAction - doOffset: |
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.smd.wily.hostagent.action.AbstractAction.doStartTimeAndOffset(AbstractAction.java:246)
at com.sap.smd.eem.agelet.EEMAction.doStartTimeAndOffset(EEMAction.java:133)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:75)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
| Sep 21, 2015 7:38:16 AM [Thread[ExRun:WILYHOST_SCHEDULER_23,5,WILYH...] Error | com.sap.smd.wily.hostagent.action.AbstractAction - doOffset: |
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.smd.wily.hostagent.action.AbstractAction.doStartTimeAndOffset(AbstractAction.java:246)
at com.sap.smd.eem.agelet.EEMAction.doStartTimeAndOffset(EEMAction.java:133)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:75)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
| Sep 21, 2015 7:38:16 AM [Thread[ExRun:WILYHOST_SCHEDULER_25,5,WILYH...] Error | com.sap.smd.wily.hostagent.action.AbstractAction - doOffset: |
[EXCEPTION]
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at com.sap.smd.wily.hostagent.action.AbstractAction.doStartTimeAndOffset(AbstractAction.java:246)
at com.sap.smd.eem.agelet.EEMAction.doStartTimeAndOffset(EEMAction.java:133)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:75)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
And this is fromt the agent trace file:
#1.5 #020085E2EC0402DA00000001000013700005203B3372C936#1442813522465#com.sap.smd.eem.executor.XmlExecutor##com.sap.smd.eem.executor.XmlExecutor.iteration#######Thread[EEM/EP5510A_Equipment_aendern Trier 70011768/1,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Error##Java###Script execution aborted
[EXCEPTION]
{0}#1#com.sap.smd.eem.executor.ExecutorException: result status reaches threshold (FAILED)
at com.sap.smd.eem.executor.XmlExecutor.runStep(XmlExecutor.java:217)
at com.sap.smd.eem.executor.XmlExecutor.iteration(XmlExecutor.java:44)
at com.sap.smd.eem.executor.AbstractExecutor.run(AbstractExecutor.java:205)
at com.sap.smd.eem.agelet.EEMAction.doRun(EEMAction.java:152)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:90)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
#
#1.5 #020085E2EC0402DB00000000000013700005203B33A91B12#1442813526025#com.sap.smd.eem.executor.XmlExecutor##com.sap.smd.eem.executor.XmlExecutor.iteration#######Thread[EEM/EQ5510A_ih06a/1,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Error##Java###Script execution aborted
[EXCEPTION]
{0}#1#com.sap.smd.eem.executor.ExecutorException: result status reaches threshold (FAILED)
at com.sap.smd.eem.executor.XmlExecutor.runStep(XmlExecutor.java:217)
at com.sap.smd.eem.executor.XmlExecutor.iteration(XmlExecutor.java:44)
at com.sap.smd.eem.executor.AbstractExecutor.run(AbstractExecutor.java:205)
at com.sap.smd.eem.agelet.EEMAction.doRun(EEMAction.java:152)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:90)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
#
#1.5 #020085E2EC0402DC00000000000013700005203B33E74A6D#1442813530101#com.sap.smd.eem.executor.XmlExecutor##com.sap.smd.eem.executor.XmlExecutor.iteration#######Thread[EEM/EQ5510A_ih06b/1,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Error##Java###Script execution aborted
[EXCEPTION]
{0}#1#com.sap.smd.eem.executor.ExecutorException: result status reaches threshold (FAILED)
at com.sap.smd.eem.executor.XmlExecutor.runStep(XmlExecutor.java:217)
at com.sap.smd.eem.executor.XmlExecutor.iteration(XmlExecutor.java:44)
at com.sap.smd.eem.executor.AbstractExecutor.run(AbstractExecutor.java:205)
at com.sap.smd.eem.agelet.EEMAction.doRun(EEMAction.java:152)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:90)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
#
#1.5 #020085E2EC0402DD00000000000013700005203B341ED198#1442813533740#com.sap.smd.eem.executor.XmlExecutor##com.sap.smd.eem.executor.XmlExecutor.iteration#######Thread[EEM/EQ5510A_ih06c/1,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Error##Java###Script execution aborted
[EXCEPTION]
{0}#1#com.sap.smd.eem.executor.ExecutorException: result status reaches threshold (FAILED)
at com.sap.smd.eem.executor.XmlExecutor.runStep(XmlExecutor.java:217)
at com.sap.smd.eem.executor.XmlExecutor.iteration(XmlExecutor.java:44)
at com.sap.smd.eem.executor.AbstractExecutor.run(AbstractExecutor.java:205)
at com.sap.smd.eem.agelet.EEMAction.doRun(EEMAction.java:152)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:90)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
#
#1.5 #020085E2EC0402DE00000000000013700005203B3615CF91#1442813566706#com.sap.smd.eem.executor.XmlExecutor##com.sap.smd.eem.executor.XmlExecutor.iteration#######Thread[EEM/il03a/1,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Error##Java###Script execution aborted
[EXCEPTION]
{0}#1#com.sap.smd.eem.executor.ExecutorException: result status reaches threshold (FAILED)
at com.sap.smd.eem.executor.XmlExecutor.runStep(XmlExecutor.java:217)
at com.sap.smd.eem.executor.XmlExecutor.iteration(XmlExecutor.java:44)
at com.sap.smd.eem.executor.AbstractExecutor.run(AbstractExecutor.java:205)
at com.sap.smd.eem.agelet.EEMAction.doRun(EEMAction.java:152)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:90)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
#
#1.5 #020085E2EC0402DF00000000000013700005203B365887F6#1442813571080#com.sap.smd.eem.executor.XmlExecutor##com.sap.smd.eem.executor.XmlExecutor.iteration#######Thread[EEM/KP1140A_Dispoliste_anzeigen/1,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Error##Java###Script execution aborted
[EXCEPTION]
{0}#1#com.sap.smd.eem.executor.ExecutorException: result status reaches threshold (FAILED)
at com.sap.smd.eem.executor.XmlExecutor.runStep(XmlExecutor.java:217)
at com.sap.smd.eem.executor.XmlExecutor.iteration(XmlExecutor.java:44)
at com.sap.smd.eem.executor.AbstractExecutor.run(AbstractExecutor.java:205)
at com.sap.smd.eem.agelet.EEMAction.doRun(EEMAction.java:152)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:90)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
#
#1.5 #020085E2EC0402E000000000000013700005203B36AB862B#1442813576518#com.sap.smd.eem.executor.XmlExecutor##com.sap.smd.eem.executor.XmlExecutor.iteration#######Thread[EEM/KP1140A_PMWC_PER_TEST/1,5,WILYHOST_SCHEDULER:ExecTG]##0#0#Error##Java###Script execution aborted
[EXCEPTION]
{0}#1#com.sap.smd.eem.executor.ExecutorException: result status reaches threshold (FAILED)
at com.sap.smd.eem.executor.XmlExecutor.runStep(XmlExecutor.java:217)
at com.sap.smd.eem.executor.XmlExecutor.iteration(XmlExecutor.java:44)
at com.sap.smd.eem.executor.AbstractExecutor.run(AbstractExecutor.java:205)
at com.sap.smd.eem.agelet.EEMAction.doRun(EEMAction.java:152)
at com.sap.smd.wily.hostagent.action.AbstractAction.run(AbstractAction.java:90)
at com.sap.smd.wily.hostagent.Scheduler$RunnerAdapter.run(Scheduler.java:165)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:46)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:781)
at java.lang.Thread.run(Thread.java:761)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- App to automatically configure a new ABAP Developer System in Technology Blogs by Members
- Hack2Build on Business AI – Highlighted Use Cases in Technology Blogs by SAP
- SAP Partners unleash Business AI potential at global Hack2Build in Technology Blogs by SAP
- Analyze Expensive ABAP Workload in the Cloud with Work Process Sampling in Technology Blogs by SAP
- SAP Analytics Cloud - Performance statistics and zero records in Technology Blogs by SAP
| User | Count |
|---|---|
| 90 | |
| 10 | |
| 10 | |
| 10 | |
| 7 | |
| 7 | |
| 6 | |
| 5 | |
| 4 | |
| 3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.