allbory wrote:Well, double check them anyways.
1. I'm sure that there's no memory leakage to use connection/preparedstatement/callablestatemet.
Then should I close ArrayList after use of it by using below way?You can't close ArrayLists. And you would only want to null them in case you knew you were hanging on to the references for longer than needed. And you wouldn't be asking this question if you were.arrayname = null;
Right now I'm suspicious ArrayList memory leakage. But I don't know how to check this out.ArrayList doesn't leak memory. Although it can allocate memory poorly, if you rely on the default growth pattern and fill it with let's say a million objects.
2. I just opened dump file and tried to find any clue but I couldn't figure it out.If only it was that easy. Then you wouldn't need to analyze anything.
Is there any tools or file that can say which class file got memory leakage?
allbory wrote:What you do is put this on the test box. Create some normal traffic that mimics what should happen.
tried to find any clue but I couldn't figure it out.