Monitoring the JVM server in CICS with IBM Support Assistant

From the developerWorks archives

Adam Rice

Date archived: July 26, 2016 | First published: March 13, 2013

Memory leaks in Java programs can be as critical as they are in programs written in other languages. While Java has a Garbage Collector, it sometimes cannot remove objects because they are still referenced. Therefore memory leaks require you to first, locate them, and second, identify the class responsible. This article uses a sample Java program running in the CICS JVM server to show you how to locate a memory leak and identify the class responsible.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=861538
ArticleTitle=Monitoring the JVM server in CICS with IBM Support Assistant
publish-date=03132013