Having critical less than warning does not work

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by [email protected] on 19 Dec 2012 at 6:14

[GoogleCodeExporter]

I did some testing, it was working in 1.0 but does not work in 1.1, 1.2 and 
1.3.  Thank  you!

Original comment by [email protected] on 19 Dec 2012 at 6:28

[GoogleCodeExporter]

Still appears to be an issue in the latest snapshot.

Original comment by [email protected] on 11 Sep 2013 at 4:54

[GoogleCodeExporter]

I think I've fixed this.  Attached is a patch.  Can someone in the project 
apply it?

Original comment by [email protected] on 12 Sep 2013 at 7:24

Attachments:

• invert.diff