-
1. Re: Possible Memory Leak
peterj Jan 29, 2010 10:41 AM (in response to mayankmit2002)Does this post reflect the same thing you are seeing:
-
2. Re: Possible Memory Leak
mayankmit2002 Jan 31, 2010 11:02 PM (in response to peterj)peterj wrote:
Does this post reflect the same thing you are seeing:
Yes, The problem is almost similar to that of what explained in the specified post, but with few discrepancies, in the specified post, the guy starts facing problem when he upgrade its AS from JBoss 4.2.3 to JBoss 5.1.0. But I'm facing the problem on Jboss 4.2.3, evev i tried with the latest JVM version 1.6.0u18, But the outcome is the same.
-
3. Re: Possible Memory Leak
peterj Feb 1, 2010 1:01 PM (in response to mayankmit2002)I don't know enough about the debugging tools available on Linux to provide much help. The only thing that comes to mind is to use a C/C++ debugger attached to the java process to see if that helps identify where and why the memory is being allocated. -
4. Re: Possible Memory Leak
mayankmit2002 Feb 10, 2010 10:02 AM (in response to peterj)peterj wrote:
I used Yourkit profiler as well as JBuilder to profile the application, but any kind of memory leak is not visible, also the memory consumption keeps on increasing.
The one thing I noticed after long term execution of my server, is that, after consuming 67% of memory, linux starts using swap memory instead of RAM. Can you throw some light on this behavior of the Linux.
-
5. Re: Possible Memory Leak
peterj Feb 10, 2010 11:39 AM (in response to mayankmit2002)Yourkit and JBuilder are Java debuggers. I wrote that you need to us a C/C++ debugger and debug the JVM itself. That is the only way you can track down a memory leak that is occurring somewhere other than in the heap or permgen.
Linux tends to use RAM only until the RAM usage is at a certain level, at which time it starts using the swap space. It will never use 100% of RAM (or at least ot should not be configured to) because it needs to keep some free room for loading in new apps. I do not know what configuration setting governs this, google might provide enlightenment.