We run Java VMs with 3G heap. Looks like the check_jmx plugin can handle only upto a value of 1G for cammand line option of -w and -c.
Sourcecode doesn't come with the plugin. I can volunteer to fix the code. Where can i get the source code? [EMAIL PROTECTED] plugin]# ./check_jmx -U service:jmx:rmi:///jndi/rmi://scproluap04-mgmt:9134/jmxrmi -O java.lang:type=Memory -A HeapMemoryUsage -K used -I HeapMemoryUsage -J used -vvvv -w 1099577209 -c 1246194688 JMX CRITICAL HeapMemoryUsage.used=2141276184{committed=3246194688;init=3246391296;max=3246194688;used=2141276184} [EMAIL PROTECTED] plugin]# ./check_jmx -U service:jmx:rmi:///jndi/rmi://scproluap04-mgmt:9134/jmxrmi -O java.lang:type=Memory -A HeapMemoryUsage -K used -I HeapMemoryUsage -J used -vvvv -w 1099577209 -c 3000000000 JMX UNKNOWN java.lang.NumberFormatException: For input string: "3000000000" connecting to java.lang:type=Memory by URL service:jmx:rmi:///jndi/rmi://scproluap04-mgmt:9134/jmxrmiorg.nagios.ParseError: java.lang.NumberFormatException: For input string: "3000000000" at org.nagios.JMXQuery.parse(JMXQuery.java:250) at org.nagios.JMXQuery.main(JMXQuery.java:74) Caused by: java.lang.NumberFormatException: For input string: "3000000000" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:459) at java.lang.Integer.parseInt(Integer.java:497) at org.nagios.JMXQuery.parse(JMXQuery.java:242) ... 1 more Usage: check_jmx -help ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null