gohopper / jmxquery Goto Github PK

It would be extremely useful to be able to check memory usage with percent 
based warning and critical levels. 

So if the memory is updated on the JMX you would not have to update the nagios 
monitor.

What steps will reproduce the problem?
1. check_jmx -username foo -password bar 

What is the expected output? What do you see instead?
The password bar shows up in process lists, which is potentially a security 
issue.

What version of the product are you using? On what operating system?
1.3, linux (Red Hat Enterprise linux 6.4)

Please provide any additional information below.

Attached is modified JMXQuery.java which adds a -pwfile option, allowing you to
provide the name of a file containing the password instead of the password 
itself
on the command line. The specified password file should have the plaintext 
password
as the sole contents of the first line of the file.  File permissions should be 
set
to restrict read access to those authorized to use the password.

WARNING: I am not comfortable programming in Java, so while my modifications 
appear to work and do not appear to break any existing functionality, a review 
by an experienced Java programmer is certainly called for.  Error reporting 
could use improvement also.

NOTE: password will still be sent unencrypted over the wire unless SSL is also 
used.

Instead of simple warning and critical thresholds, can the plugin check the 
value returned and if it's not matching (simple regex would suffice) return 
critical and if it matches return ok?

Added the ability to invoke methods, on MBeans, that takes parameters.

the syntax to pass parameters is:

jmxquery -U service:jmx:remoting-jmx://server:9999 -u administrator -p password 
-O org.test:name=testService -M testMethod -P parameter1  "parameter 2"

- I created a the CollectionArrayUtils class that contains some utils about 
conversion from/to array and collection

- I modified some logic in the class JMXQuery

What steps will reproduce the problem?
1. svn co …/trunk
2. mvn package
3.

What is the expected output? What do you see instead?

Should produce a jar in target/

Instead produces compile errors complaining that we're not targeting Java 1.5.

What version of the product are you using? On what operating system?

trunk on MacOS

Please provide any additional information below.

I've attached a patch which fixes this.

What steps will reproduce the problem?
1. ./check_jmx -U 
service:jmx:iiop:///jndi/iiop://<IP>:<PORT>/weblogic.management.mbeanservers.run
time -O java.lang:type=Threading -A ThreadCount -K value -username <user_name> 
-password >password> -w 40 -c 800

JMX CRITICAL

2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?

I am using SUN JDK
Java(TM) SE Runtime Environment (build 1.6.0_32-b05)
Java HotSpot(TM) Server VM (build 20.7-b02, mixed mode)

I am connecting to weblogic (on Jrockit) on WLS 10.3.0

Please provide any additional information below.

What steps will reproduce the problem?
1. run check_jmx 
2. observe that it does not produce any performance output

What is the expected output? What do you see instead?
|attrib=value;;;;

What version of the product are you using? On what operating system?
1.0, CentOS 5.5

Please provide any additional information below.

Hi guys,

thanks for the plugin! I added an comparator parameter which allows to check 
for >=, >, <=, < and = for Comparable java types. (In this case Long and 
Double).

You can use it like:
jmxquery.jar [...] -comparator >=
jmxquery.jar [...] -comparator >
jmxquery.jar [...] -comparator <=
jmxquery.jar [...] -comparator <
jmxquery.jar [...] -comparator =

I attached a "patch" to share this feature with you.

What steps will reproduce the problem?
./check_jmx -U service:jmx:rmi:///jndi/rmi://WWW.XXX.YYY.ZZZ:8080/jmxrmi -O 
org.apache.cassandra.db:type=CompactionManager -A ColumnFamilyInProgress   
JMX CRITICAL - null


What is the expected output? What do you see instead?
An extra arguement which would allow converting the text output from null to 0, 
so that you can then assign warn/critical thresholds

What version of the product are you using? On what operating system?
SunOS - 5.10 Generic_141414-10 sun4v sparc SUNW,Sun-Fire-T200

and

Distributor ID: Ubuntu
Description:    Ubuntu 10.10
Release:        10.10
Codename:       maverick

Code version: jmxquery-1.0

Please provide any additional information below.

I have also noticed when you try and produce a verbose output that this creates 
an error

./check_jmx -U service:jmx:rmi:///jndi/rmi://WWW.XXX.YYY.ZZZ:8080/jmxrmi -O 
org.apache.cassandra.db:type=CompactionManager -A ColumnFamilyInProgress -v
JMX CRITICAL - null

./check_jmx -U service:jmx:rmi:///jndi/rmi://WWW.XXX.YYY.ZZZ:8080/jmxrmi -O 
org.apache.cassandra.db:type=CompactionManager -A ColumnFamilyInProgress -vv
JMX CRITICAL - null connecting to 
org.apache.cassandra.db:type=CompactionManager by URL 
service:jmx:rmi:///jndi/rmi://WWW.XXX.YYY.ZZZ:8080/jmxrmi

./check_jmx -U service:jmx:rmi:///jndi/rmi://WWW.XXX.YYY.ZZZ:8080/jmxrmi -O 
org.apache.cassandra.db:type=CompactionManager -A ColumnFamilyInProgress -vvv
JMX CRITICAL - null connecting to 
org.apache.cassandra.db:type=CompactionManager by URL 
service:jmx:rmi:///jndi/rmi://WWW.XXX.YYY.ZZZ:8080/jmxrmijava.lang.NullPointerEx
ception
        at jmxquery.JMXQuery.parseData(JMXQuery.java:231)
        at jmxquery.JMXQuery.execute(JMXQuery.java:210)
        at jmxquery.JMXQuery.main(JMXQuery.java:90)

We want to use jmxquery to grab C3P0 connection pool parameters, unfortunately, 
the objectname JMX Bean is randomly generated/picked by C3P0 like 
com.mchange.v2.c3p0:type=PooledDataSource[1hge1ca8bna6zgq1fj33q6|77a3e2f7]

Seems like there's no way we can set this name up at deployment time, I would 
appreciate a way we can define a wild card pattern instead of a specific 
objectname in the command, and dump the content of the first match element.

So the changes will be something like this:

        Object attr = null;

        if(wildcard){
            Set<ObjectName> names = connection.queryNames(new ObjectName(object),null );
            if(names!=null&& names.size()>0){
                ObjectName name = names.iterator().next();
                attr = connection.getAttribute(name, attribute);
            }
        }else
            attr = connection.getAttribute(new ObjectName(object), attribute);

Would you please let me know your thoughts?

Thanks a lot

Eric

What steps will reproduce the problem?
1. connect JConsole to the target host; open "Threads" tab
2. execute any valid check_jmx command; observe that a new thread was
created on the server
3. repeat #2 N times; observe that N new threads are created

The problem is that JMXQuery.main System.exit()'s *before* closing the
connection (rev 7). This means that underlying socket remains open and a
JMX Timeout thread created on the server-side remains alive for ~ 2
minutes, at which point it (hopefully) closes the connection before being
destroyed. 

The impact is this: the more frequent jmx_check invocations are, the more
extra threads will be live on the server, and the more connections will
remain open. Eventually a server may slow down or stop responding to (any!)
connection requests ;-

to fix: *always* attempt to close the connection before exiting.

What steps will reproduce the problem?
1. use an jmx object with a space in its name
2. call check (see below)
3. get the error InstanceNotFoundException wfor a name that is cut of after the 
space.

What is the expected output? What do you see instead?

I should be able to specify JMX Object names that contain a space like 
"name=Primitive count".
I tried \ and varoius combinations of single and double quotes.


What version of the product are you using? On what operating system?
1.3 on linux


Please provide any additional information below.

Thats an excerpt from my shell while testing:

# /tmp/jmxquery-1.3/check_jmx -username "monitor" -password Neo4J  -U 
"service:jmx:rmi:///jndi/rmi://neo4j:3637/jmxrmi" -O 
'org.neo4j:instance=kernel#0,name=Primitive count' -A "NumberOfNodeIdsInUse" 
-vvv
JMX CRITICAL - org.neo4j:instance=kernel#0,name=Primitive connecting to 
org.neo4j:instance=kernel#0,name=Primitive by URL 
service:jmx:rmi:///jndi/rmi://urmel-stage01.l3muc.inside:3637/jmxrmijavax.manage
ment.InstanceNotFoundException: org.neo4j:instance=kernel#0,name=Primitive
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1094)
    at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:662)
    at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:638)
    at com.sun.jmx.remote.security.MBeanServerAccessController.getAttribute(MBeanServerAccessController.java:299)
    at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1404)
    at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
    at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
    at javax.management.remote.rmi.RMIConnectionImpl.getAttribute(RMIConnectionImpl.java:600)
    at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
    at sun.rmi.transport.Transport$1.run(Transport.java:159)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662)
    at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255)
    at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
    at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
    at javax.management.remote.rmi.RMIConnectionImpl_Stub.getAttribute(Unknown Source)
    at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.getAttribute(RMIConnector.java:880)
    at jmxquery.JMXQuery.execute(JMXQuery.java:230)
    at jmxquery.JMXQuery.runCommand(JMXQuery.java:69)
    at jmxquery.JMXQuery.main(JMXQuery.java:114)

Adding a pipe to output perf data would be greatly helpful in graphing jmx 
stats.

Here is an improved version of check_jmx bash script, one that will detect 
JAVA_HOME and that fails nicely when JAVA is missing.

#!/bin/sh
#
# Nagios plugin to monitor Java JMX (http://java.sun.com/jmx)attributes.
#
#RDIR=`dirname $0`
#java -cp $RDIR/jmxquery.jar org.nagios.JMXQuery $@

#!/bin/sh
JAVA_CMD=`which java`
if [ -z $JAVA_CMD ]; then
    if [ -x $JAVA_HOME/bin/java ]; then
<------>JAVA_CMD=$JAVA_HOME/bin/java
    else
<------>echo JMX CRITICAL - java not found.
<------>exit 2
    fi
fi

RDIR=`dirname $0`
OUTPUT=$($JAVA_CMD -jar $RDIR/jmxquery.jar $@)
EXIT_STATUS=$?
STATUS=`echo $OUTPUT`
VALUE=$(echo $OUTPUT | sed 's/.*{\(.*\)}.*/\1;/' | sed 's/;/; /g')
echo "$STATUS | $VALUE"

exit $EXIT_STATUS.

What steps will reproduce the problem?
# ./check_jmx -U 
service:jmx:rmi:///jndi/rmi://10.10.10.10:50500/alfresco/jmxrmi -O 
java.lang:type=Memory -A HeapMemoryUsage -K used -I HeapMemoryUsage -J used 
-vvvv -w 10 -c 100 -username monitorRole -password change_asap
JMX CRITICAL - HeapMemoryUsage.used=415501352 | 
HeapMemoryUsage.used=415501352,committed=2619736064;init=2684354560;max=26197360
64;used=415501352

# ./check_jmx -U 
service:jmx:rmi:///jndi/rmi://10.10.10.10:50500/alfresco/jmxrmi -O 
java.lang:type=Memory -A HeapMemoryUsage -K used -I HeapMemoryUsage -J used 
-vvvv -w 10 -c 100 -username monitorRole -password change_asap
JMX CRITICAL - HeapMemoryUsage.used=449934952 | 
HeapMemoryUsage.used=449934952,committed=2619736064;init=2684354560;max=26197360
64;used=449934952

In the 1st example, critical is more than warning, the return value is more 
than both, this is working as expected.

In the 2st example, critical is less than warning, the return value is more 
than both, still return critial.

What is the expected output? What do you see instead?
Should return OK when critial is less than warning and the return is more than 
both.

What version of the product are you using? On what operating system?
jmxquery-1.3

Please provide any additional information below.

What steps will reproduce the problem?
1. how can add check_jmx in opsview tool.
2.
3.

What is the expected output? What do you see instead?
check the jvm and memory status

What version of the product are you using? On what operating system?
opsview 3.1 centos 5

Please provide any additional information below.

Some mbean attributes can have long values, for example in 
java.lang:type=Memory, if used on a 
64-bit JVM. I have attached a patch which replaces int with long throughout the 
code in JMXQuery.java.

I am monitoring JMX attributes with nagios plugin check_jmx. When type jps in 
my Linux environment i saw mutiple processes named JMXQuery and the system 
hangs after that. I think this plugin spawns these processes. What is the 
reason for that and how this plugin works? How can I fix this issue?

Not an issue but functional suggestion.

What steps will reproduce the problem?
1. Checking memory usage
2.
3.

What is the expected output? What do you see instead?
I would prefer to see % or MB/GB


What version of the product are you using? On what operating system?
1.3


Please provide any additional information below.

What steps will reproduce the problem?
1. mvn package
2. java -jar target/jmxquery-1.0-SNAPSHOT.jar
3.

What is the expected output? What do you see instead?

Should see "Usage: check_jmx -help".  Instead I see nothing.

What version of the product are you using? On what operating system?

trunk on Mac OS X.

Please provide any additional information below.

Attached is a patch which corrects this.

What steps will reproduce the problem?
1. ./check_jmx -U service:jmx:rmi:///jndi/rmi://x.y.z.k:8008/jmxrmi -O 
java.lang:type=MemoryPool,name=PS Perm Gen  -A Usage -K used -I Usage -J used 
-vv -w 10000000 -c 100000000

JMX CRITICAL - java.lang:type=MemoryPool,name=PS connecting to 
java.lang:type=MemoryPool,name=PS by URL 
service:jmx:rmi:///jndi/rmi://x.y.z.k:8008/jmxrmi

2. ./check_jmx -U service:jmx:rmi:///jndi/rmi://x.y.z.k:8008/jmxrmi -O 
java.lang:type=MemoryPool,name="PS Perm Gen"  -A Usage -K used -I Usage -J used 
-vv -w 10000000 -c 100000000

Same error 

3. ./check_jmx -U service:jmx:rmi:///jndi/rmi://x.y.z.k:8008/jmxrmi -O 
"java.lang:type=MemoryPool,name=PS Perm Gen"  -A Usage -K used -I Usage -J used 
-vv -w 10000000 -c 100000000

Same error

What is the expected output? What do you see instead?

Expected: Normal output
Instead: JMX CRITICAL - java.lang:type=MemoryPool,name=PS connecting to 
java.lang:type=MemoryPool,name=PS by URL 
service:jmx:rmi:///jndi/rmi://x.y.z.k:8008/jmxrmi


What version of the product are you using? On what operating system?

1.0
Red Hat Enterprise Linux ES release 4 (Nahant Update 4)
java version "1.5.0_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05)
Java HotSpot(TM) Server VM (build 1.5.0_13-b05, mixed mode)

Please provide any additional information below.

What steps will reproduce the problem?
1. /usr/local/nagios/libexec/check_jmx -U
service:jmx:rmi:///jndi/rmi://192.168.1.14:9999/jmxrmi -O 
java.lang:type=Memory -A HeapMemoryUsage -K used -w 975500000 -c 990000000 
2. JMX CRITICAL jmxrmi

3.

What is the expected output?  
JMX OK
HeapMemoryUsage=7715400{committed=12337152;init=0;max=66650112;used=7715400}


What version of the product are you using? On what operating system?
opsview 3.1  ,centos 5

Please provide any additional information below.
I have to add check_jmx at /usr/local/nagios/libexec location.

Please may I have contributor access to this project.

I've prepared a patch to solve a problem we have had when using the plugin to 
return monitoring information.

It now returns performance data, and also no longer errors if -w and/or -c are 
not set.

Patch attached for review.

What steps will reproduce the problem?
1. Modify check_jmx to:-

java -Djavax.net.ssl.trustStore=cacerts.jts
-Djavax.net.ssl.trustStorePassword=testing -cp $RDIR/jmxquery.jar
jmxquery.JMXQuery $@

2. Use the modified .jar file posted on these issues boards..

3. Then run then run:-

./check_jmx -U service:jmx:rmi:///jndi/rmi://localhost:17300/jmxrmi -O
java.lang:type=Memory -A HeapMemoryUsage -K used -I HeapMemoryUsage -J used
-vvvv -w 731847066 -c 1045495808 -username monitorRole -password test


What is the expected output? What do you see instead?
JMX CRITICAL - error during JRMP connection establishment; nested exception is:
javax.net.ssl.SSLHandshakeException: Received fatal alert:
handshake_failure connecting to java.lang:type=Memory by URL
service:jmx:rmi:///jndi/rmi://anise.semantico.net:17300/jmxrmijava.rmi.ConnectIO
Exception:
error during JRMP connection establishment; nested exception is:
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:274)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source)
at
javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2229)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:271)
at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248
)
at jmxquery.JMXQuery.connect(JMXQuery.java:64)
at jmxquery.JMXQuery.main(JMXQuery.java:89)
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert:
handshake_failure
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:150)
at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:117)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1542)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:863)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl
.java:1025)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:619)
at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.DataOutputStream.flush(DataOutputStream.java:106)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
... 8 more


What version of the product are you using? On what operating system?
debian sarge with sun java 5 talking to a tomcat6 running on jdk1.6.0_06

Please provide any additional information below.

What steps will reproduce the problem?
I've tried to patch original jmxquery to enable -N option
After patch, when I try to run other option it doesn't work

What is the expected output? What do you see instead?
Expected output is : 
check_jmx -vvv -U service:jmx:rmi:///jndi/rmi://10.230.3.68:2099/jmxrmi -O 
java.lang:type=ClassLoading -A LoadedClassCount
JMX OK - LoadedClassCount is 19105

Received error output :

 check_jmx -vvv -U service:jmx:rmi:///jndi/rmi://10.230.3.68:2099/jmxrmi -O java.lang:type=ClassLoading -A LoadedClassCount
JMX CRITICAL - NullPointerException: null connecting to 
java.lang:type=ClassLoading by URL 
service:jmx:rmi:///jndi/rmi://10.230.3.68:2099/jmxrmijava.lang.NullPointerExcept
ion
        at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:991)
        at java.lang.Double.parseDouble(Double.java:510)
        at jmxquery.JMXQuery.compare(JMXQuery.java:199)
        at jmxquery.JMXQuery.report(JMXQuery.java:147)
        at jmxquery.JMXQuery.main(JMXQuery.java:93)



What version of the product are you using? On what operating system?
1.0

Please provide any additional information below.

What steps will reproduce the problem?
1. check service with levels c>w
/usr/bin/java -Xmx48m -jar /usr/lib/nagios/plugins/contrib/jmxquery.jar -U 
service:jmx:rmi:///jndi/rmi://127.0.0.1:11000/jmxrmi -O 
com.panbet:type=type,name=Monitor -A PerMinute -w 30 -c 50; echo $?
JMX CRITICAL - PerMinute=443 | PerMinute=443
2


2. check service with levels w>c
/usr/bin/java -Xmx48m -jar /usr/lib/nagios/plugins/contrib/jmxquery.jar -U 
service:jmx:rmi:///jndi/rmi://127.0.0.1:11000/jmxrmi -O 
com.panbet:type=type,name=Monitor -A PerMinute -w 50 -c 30; echo $?
JMX CRITICAL - PerMinute=443 | PerMinute=443
2

3. Eror lewel outputs are the same, but must be different:
Note that if warning level > critical, system checks object attribute value to 
be LESS THAN OR EQUAL warning, critical
If warning level < critical, system checks object attribute value to be MORE 
THAN OR EQUAL warning, critical 


version of jmxquery.jar - 1.3

What steps will reproduce the problem?
1. run check_jmx against remote host:
./check_jmx -U service:jmx:rmi:///jndi/rmi://172.24.4.8:8686/jmxrmi -O 
java.lang:type=Memory -A NonHeapMemoryUsage -K used -vvvv

What is the expected output? What do you see instead?

expected: normal plugin output
instead:

JMX CRITICAL - Connection refused to host: 127.0.0.2; nested exception is: 
        java.net.ConnectException: Connection refused connecting to java.lang:type=Memory by URL service:jmx:rmi:///jndi/rmi://172.24.4.8:8686/jmxrmijava.rmi.ConnectException: Connection refused to host: 127.0.0.2; nested exception is: 
        java.net.ConnectException: Connection refused

it tries to connect to 127.0.0.2 instead of 172.24.4.8

Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
Description:    Ubuntu 8.04.3 LTS
jmxquery 1.0
Please provide any additional information below.

What steps will reproduce the problem?
1. The command used and output is below.
./check_jmx -U service:jmx:rmi:///jndi/rmi://localhost:8686/jmxrmi -O 
java.lang:type=Memory -A HeapMemoryUsage -K used -I HeapMemoryUsage -J used 
-vvvv -w 731847066 -c 1045495808 -username admin -password adminadmin
JMX OK - HeapMemoryUsage.used=94996088 | 
HeapMemoryUsage.used=94996088,committed=373665792;init=16777216;max=2075918336;u
sed=94996088

What is the expected output? What do you see instead?

According to Nagios documentation, 
(http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN201) it should 
be in the format below

'label'=value[UOM];[warn];[crit];[min];[max]

What version of the product are you using? On what operating system?
1.3 on Ubuntu hitting Glassfish 2.2 JVM

Please provide any additional information below.

First, it was a joy to find this project because it actually worked.  I was 
planning to build a pnp4nagios template using the performance data output, but 
I don't think the HeapMemoryUsage values are mapped properly.

The plugin does not seem to be able to evaluate a floating point number, for 
example 0.753940 would be reported as 0 instead.

What steps will reproduce the problem?
1. java -cp jmxquery.jar -U service:jmx:rmi:///jndi/rmi://app8:9997/jmxrmi
-O java.lang:type=Memory -A HeapMemoryUsage -K used -I HeapMemoryUsage -J
used -vvvv
2. Have a 4GB or greater heap for the running process
3.

What is the expected output? What do you see instead?
OK - HeapMemoryUsage.used is
3300064800,committed=4286251008;init=2147483648;max=4286251008;used=3300064800
instead
CRITICAL - HeapMemoryUsage.used is
-659505464,committed=4286251008;init=2147483648;max=4286251008;used=3635461832


What version of the product are you using? On what operating system?
1.0

Please provide any additional information below.
Need this parseData method
    private long parseData( Object o )
    {
        if( o instanceof Number ) return ( ( Number ) o ).longValue();
        else return Long.parseLong( o.toString() );
    }