luisdalves / jmxquery

Automatically exported from code.google.com/p/jmxquery
0 stars 0 forks source link

Empty spaces on Object name to be checked #16

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
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.

Original issue reported on code.google.com by sierrabr...@gmail.com on 3 Mar 2011 at 5:39

GoogleCodeExporter commented 8 years ago
I try this:

java  -cp jmxquery.jar jmxquery.JMXQuery -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 WARNING - Usage.used is 9250235292502352

It works!

I think that shell script needs to be fixed.

Original comment by sierrabr...@gmail.com on 4 Mar 2011 at 8:54

GoogleCodeExporter commented 8 years ago
Solved by editing check_jmx shell script.

Replace $@ with "$@"

Original comment by sierrabr...@gmail.com on 4 Mar 2011 at 10:31