h3. Introduction Sometimes when a JEE application is stopped, restarted or redeployed on the SAP NetWeaver platform the ClassLoader associated with this application is not properly removed from the heap. This can lead on one side to resource problems...

In my Memory for nothing I have described how memory "wasted" for unused collections can be identified using the SAP Memory Analyzer tool. This can often help one to get some reduction in the memory footprint quickly and easily. This time I will desc...

Introduction In my Finding Memory Leaks with SAP Memory Analyzer I have described a general method to search for memory leaks using the SAP Memory Analyzer tool. This time I will describe a very concrete pattern for “wasting” heap in Java.In many of ...

IntroductionThere is a common understanding that a single snapshot of the java heap is not enough for finding a memory leak. The usual approach is to search for a monotonous increase of the number of objects of some class by “online” profiling/monito...