In a previous article, we discussed about the use of Rational Purify to detect the memory leaks in one of the applications that was developed using J2EE technology. We have also discussed briefly about the analysis procedure and given some suggestions to avoid memory leaks. In this paper (on the basis of the feedback received in my teaching session on Purify), we are discussing a hands-on exercise (MemoryLeaksAfter.java) to give a close insight to understand memory leaks and their prevention. The program was tested using Purify and the results obtained from such a study are discussed here.
In a previous article, we discussed about the use of Rational Purify to detect the memory leaks in one of the applications that was developed using J2EE technology. We have also discussed briefly about the analysis procedure and given some suggestions to avoid memory leaks. In this paper (on the basis of the feedback received in my teaching session on Purify), we are discussing a hands-on exercise (MemoryLeaksAfter.java) to give a close insight to understand memory leaks and their prevention. The program was tested using Purify and the results obtained from such a study are discussed here.
