SAP Knowledge Base Article - Preview

2388889 - Jstart Process of Diagnostics Agent consuming high memory / CPU

Symptom

  • The jstart process of the Diagnostics Agent is consuming a huge amount of memory. After checking a Java Heap dump for the Diagnostics Agent, it is possible to see that the Agent applications are not using this much memory. This indicates an issue with the JVM of the Diagnostics Agent, that causes this memory leak.
  • When analysing the thread dumps you may see following threads taking up most usage:


com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run()V(IntervalHeartbeat.java:673)

com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run()V(IntervalHeartbeat.java:670)

com.wily.introscope.agent.connection.ConnectionThread.pauseBetweenAttempts()V(ConnectionThread.java:107)


Read more...

Environment

  • SAP Solution Manager 7.1.
  • SAP Solution Manager 7.2.
  • Diagnostics (SMD) Agent.
  • Linux Operating Systems (Potentially others effected).

Product

SAP Solution Manager 7.2

Keywords

Jstart Process of Diagnostics Agent consuming high memory – Solution Manager 7.1 and 7.2 Diagnostics (SMD) , KBA , SV-SMG-DIA-SRV-AGT , Agent Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.