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
Original issue reported on code.google.com by kiva...@gmail.com on 7 Oct 2013 at 12:47
Original issue reported on code.google.com by
kiva...@gmail.com
on 7 Oct 2013 at 12:47