Actually the console reports both. scroll down.
BTW there is a nastsy bug in the 1.4.x VM where it can go into garbage collector psychosis and never leave a cycle of
repeating full garbage collections. I've only seen this with parallel setups on Solaris, but I have no reason to believe that it
can't happen on Linux. So running with the verbose gc logging is about the only way to can be sure you haven't run out of
memory. (whats worse is that the garbage collector bug can happen even if you aren't that short on memory :-) but the bug was
uncerimoniously closed because it doesn't seem to happen on 1.5 :-P)
-Andy
Jason Williams wrote:
Looks like the number reported by the console is the allocated space, but not the used space. If I keep adding objects, I eventually get the OutOfMemory error.
Jason
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jason Williams Sent: Thursday, March 24, 2005 11:52 AM To: Research Triangle Java User's Group mailing list. Subject: RE: [Juglist] jboss app memory usage
Ok. I think I found it in the jmx-console. I was able to view the JVM specs for the running application and the specs showed the current and maximum heap size. Good so far.
So, now I have another question. My application uses Lucene indexes and they are fairly large. I'm trying to determine the memory requirements to open up and search these indexes. When each one is opened, the app creates a class that holds the IndexSearcher class and some associated files. As I added each one I saw the heap size grow accordingly. Knowing that the default heap size is 64MB, as I approached that limit I fully expected to start getting OutOfMemory errors.
However, this did not happen. The heap size reported by the jmx-console caps out at 66387968 (darn close to 64MB). And as I keep adding new indexes, the heap size remains at 64MB, I get no OutOfMemory errors and my application is responding correctly.
I'm fairly certain that the other indexes have not been garbage collected and therefore should still be on the heap. So, what gives here? Is there some sort of swap space for the heap? Is the number reported by the jmx-console the max, but the actual memory being used is less?
Any thoughts?
Thanks,
Jason
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jason Williams Sent: Thursday, March 24, 2005 9:03 AM To: Triangle JUG Subject: [Juglist] jboss app memory usage
Hi guys,
How can I determine how much memory an application running in JBoss is using?
Thanks,
Jason Williams Web Commerce Group Private-label Internet Applications for Business
Home of Arkdom Managed Services www.arkdom.com
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org
_______________________________________________ Juglist mailing list [email protected] http://trijug.org/mailman/listinfo/juglist_trijug.org .
_______________________________________________ Juglist mailing list [email protected] http://trijug.org/mailman/listinfo/juglist_trijug.org
