Thanks Babak. The wildcard allowed us to return the properties of the FileConsumer with the updated command.
check_jmx -U service:jmx:rmi:///jndi/rmi://x.x.x.x:1099/jmxrmi/camel -O "*:type=consumers,*" -A State While this works well as we only have one FileConsumer in this particular application, it seems we would have an issue if we had more than one. Reading the docs located at http://camel.apache.org/camel-jmx.html we noticed the section 'Management naming pattern'. It looks like in 2.10 it will be much easier to come up with a MBean naming strategy to uniquely identify the components. -- View this message in context: http://camel.465427.n5.nabble.com/Monitoring-Camel-with-JMX-tp5646538p5646955.html Sent from the Camel - Users mailing list archive at Nabble.com.
