...
This example has 2 routes:
1. A route that calls a update method on an MBean every 5th second. This is done using a timer endpoint.
2. A route that monitors the MBean using the jmx-component. When the first route fires it causes the MBean to update and send out a notification
event. This route subscribes to that MBean and receives any JMX notification events. Events are then just sent to the log endpoint.
The idea and a plan
Usage
You can use maven to run the example using
...
It takes about 10 second before Camel logs to the screen the first time. Its should be like this
Code Block |
---|
2010-11-17 08:01:09,755 [foo ] INFO jmxEvent - Exchange[ExchangePattern:InOnly, BodyType:String, Body:<?xml version="1.0" encoding="UTF-8" standalone="yes"?><AttributeChangeNotification xmlns="urn:org.apache.camel.component:jmx"><source>jmxExample:name=simpleBean</source><message>attribute changed</message><sequence>36</sequence><timestamp>1262878215000</timestamp><dateTime>2010-01-07T10:30:15.000-05:00</dateTime><type>jmx.attribute.change</type><attributeName>stringValue</attributeName><attributeType>string</attributeType><newValue>37</newValue><oldValue>36</oldValue></AttributeChangeNotification>]
|