Hi Kiran,
thanks for your update.
As per the screenshot Nagios reports these numbers for JBoss
jboss heap memory : 34.57% used (690.21 MB / 1.95 GB)
jboss non-heap memory : 7.14% used (148.57 MB / 2.05 GB)
I actually had to check what "non-heap memory" is and found
http://blog.java-hoster.com/2011/java-course/performance/jvm-memory-and-java-heap-space
..
The non heap memory
Beside the heap memory containing the living data, the JVM needs additional information, especially classes descriptions or metadata.
All this stuff is stored in a dedicated area named Permanent generation.
..
so we are talking PermGen size here, which can be configured via this parameter
-XX:MaxPermSize=530m
in the .ini file.
This (and other) articles also talk about potential memory leaks of earlier Tomcat versions which cause the PermGen area to fill up.
BSM 9.25 (I don't have a BSM 9.24 instance, but think it's the same JBoss version) comes with
JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)
which uses embedded Tomcat version 6.0.13
Instead of blindly increasing one of the parameters in the .ini file, I would check the JBoss logiles (<HPBSM>\log\jboss*) for out of memory errors, and proceed from there
You might need to go back in history a little bit in case you implemented your pro-active DPS restart a long time ago.
You can also monitor the jvm_statistics file, I would expect tht you should be able to see an increase in the PERM area.
Greetings
Siggi
