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

• 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 Diagnostics 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 Diagnostics Agent 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)

• SAP Solution Manager 7.1.
• SAP Solution Manager 7.2.
• Diagnostics (SMD) Agent.
• Linux Operating Systems (Potentially others effected).
• JVM(Java virtual machine) 6 / 1.6

Jstart Process of Diagnostics Agent consuming high memory – Solution Manager 7.1 and 7.2 Diagnostics (SMD) SAP JVM memory allocation leak when using SMD Agent commited memory wily Agent , KBA , SV-SMG-DIA-SRV-AGT , Agent Framework , Problem