I’ve been seeing performance problems with our application which might be related to a memory leak somewhere in our codes. Even if our application is inactive the java memory heap continues to grow, and I just can’t understand why this should be happening. By using HP JTune, I was able to visualize the java memory heap usage and garbage collection activities in our test server.
There are good and bad things about this. The good thing is that when a full garbage collector kicks in, most of the unused objects are cleared up, and the bad thing is those objects shouldn’t be there after all considering there’s no activity within the system.
I have a feeling that the java memory heap usage increase might be caused by our logging modules on network connections that sends out keep-alive calls such as our SMSC module since it’s the only module that would be active even if there’s no user accessing our application.
Well, there’s only one way to find out .. furthere investigation.. 
Popularity: 3% [?]