-
1. Re: Memory issues with JBoss 4.2.2.GA
peterj Feb 6, 2009 11:08 AM (in response to bngsvcs)You are printing out the detailed GC information. Have you graphed those to see what the heap usage looks like? For hints on graphing, see my presentation at http://www.cecmg.de/doc/tagung_2007/agenda07/24-mai/2b3-peter-johnson/index.html.
Also, you are using the CMS collector, so pay attention to the slide on CMS gotchas. -
2. Re: Memory issues with JBoss 4.2.2.GA
bngsvcs Feb 6, 2009 2:27 PM (in response to bngsvcs)"PeterJ" wrote:
You are printing out the detailed GC information. Have you graphed those to see what the heap usage looks like? For hints on graphing, see my presentation at http://www.cecmg.de/doc/tagung_2007/agenda07/24-mai/2b3-peter-johnson/index.html.
Also, you are using the CMS collector, so pay attention to the slide on CMS gotchas.
I appreciate the response. And I will be reviewing those topics. But I still need to understand why the JBoss processes do not appear to be getting the space that I have attempted to allocate.
If I allocate 3GB to the JVM in the run.conf file why does the web-console tell me it only has 124MB? 124MB is not enough for this web application. -
3. Re: Memory issues with JBoss 4.2.2.GA
peterj Feb 6, 2009 2:55 PM (in response to bngsvcs)Do not rely on the data given by web-console. Use JConsole or VirtualVM to monitor real-time heap usage. Use my presentation to graph the GC data you are collecting and to help you tune the heap.
Since you set the heap to 1GB minimum, the JVM will allocate that much space. Not all will be used, In fact, the CMS collector will use a lot less of it than the default collector due to the way the CMS collector works (my presentation explains that also).
P.S. You do not have to quote the post. -
4. Re: Memory issues with JBoss 4.2.2.GA
bngsvcs Feb 6, 2009 3:26 PM (in response to bngsvcs)I just made an interesting discovery. Since this is running on a Windows platform I am using JBossService. I did not realize that it makes entries on the registry. It turns out that the parameters on the registry is what is being allocated to JBoss. What I found there was 64MB and 128MB. I changed them to 128MB and 256 MB and the web-console now shows the new settings.
In addition to this I had noticed that the web-console was showing a back level JVM. Settings for that back level JVM were also on the registry.
I really hadn't thought of the service causing a big difference between what I am running and what the documentation is describing. Obviously I needed to. So at this point I have to assume that the settings in the run.conf file don't mean anything when running JBossService.
I'll have to start researching how to change the configuration with JBossService. -
5. Re: Memory issues with JBoss 4.2.2.GA
peterj Feb 6, 2009 5:31 PM (in response to bngsvcs)Sounds like you are using the JavaService tool from http://javaservice.objectweb.org/. It has a script that creates a service named JBossService and places all configuration information in the registry. Note that that project has nothing to do with JBoss AS.
As you found out, omitting key information such as this is likely to generate no-so-helpful responses.
Finally, use of JavaService is discouraged, see http://www.jboss.org/community/docs/DOC-11932, first item under "Notes"