From: <dim...@jb...> - 2005-06-09 20:23:43
|
There is actually such an MBean: (look in deploy/monitoring-service.xml) | <mbean code="org.jboss.monitor.services.MemoryMonitor" | name="jboss.monitor:service=MemoryMonitor"> | | <attribute name="FreeMemoryWarningThreshold">17m</attribute> | <attribute name="FreeMemoryCriticalThreshold">16m</attribute> | </mbean> | There is a problem with it, if you want to use it in conjuction with the snmp-adaptor, in that it produces the same notification type (jboss.alarm.memory.low) but with a different severity level to indicate the setting or the seizure of the alarm. | public static final int SEVERITY_NORMAL = 0; | public static final int SEVERITY_WARNING = 1; | public static final int SEVERITY_MINOR = 2; | public static final int SEVERITY_MAJOR = 3; | public static final int SEVERITY_CRITICAL = 4; | public static final int SEVERITY_UNKNOWN = 5; | So you can't only rely on the notification type only to indicate the low-memory condition. This was the first effort of actually having a "stateful" alarm in jboss, something that would go into an active alarm table. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880992#3880992 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880992 |