Finding Java Memory Leaks in WebSphere Application Server

This two-part series explains how to diagnose and find the source of memory leaks in WebSphere Application Server. Part 1 focuses on Java heap leaks and two different trace formats, Sun's Hprof and IBM's heapdump, that you can use for diagnosis. Part 2 focuses on Java heap leaks and z/OS tools you can use for diagnosis.

Steve Eaton (steaton@us.ibm.com), Software Engineer, EMC

Steve Eaton is part of the WebSphere Application Server technical support team.



Frederic Mora, Software Developer, EMC

Frederic Mora has been involved in development for ten years and in WebSphere testing for three years. He also supports WebSphere on zSeries customers.



Hany Salem (hany@us.ibm.com), WebSphere Serviceability Architect, EMC

Hany Salem is the lead serviceability architect for WebSphere Application Server.



10 March 2004

This two-part series explains how to diagnose and find the source of memory leaks in WebSphere Application Server. Part 1 focuses on Java heap leaks and two different trace formats, Sun's Hprof and IBM's heapdump, that you can use for diagnosis. Part 2 focuses on Java heap leaks and z/OS tools you can use for diagnosis.

Downloads

DescriptionNameSize
Article in PDF format, Part 1 0403_mora1.pdf  ( HTTP | FTP )762 KB
Article in PDF format, Part 2 0403_mora2.pdf  ( HTTP | FTP )57 KB
static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=14479
SummaryTitle=Finding Java Memory Leaks in WebSphere Application Server
publish-date=03102004