I would attach a tracer to the route and walk through its execution. Just google "apache Camel tracer"
*Robert Simmons Jr. MSc. - Lead Java Architect @ EA* *Author of: Hardcore Java (2003) and Maintainable Java (2012)* *LinkedIn: **http://www.linkedin.com/pub/robert-simmons/40/852/a39 <http://www.linkedin.com/pub/robert-simmons/40/852/a39>* On Mon, Feb 10, 2014 at 11:18 AM, Zadko <zaqavil...@gmail.com> wrote: > Hi, > > I am working on a project and have decided to use Camel and ActiveMQ. I am > attempting to create a route using Java and MQTT endpoints. Within this > route I have also incorporated a Processor. This is what my route looks > like: > > from("mqtt:test?subscribeTopicName=zaq.avila.send") > //.process(new RestProcessor()) > > .to("mqtt:test?publishTopicName=zaq.avila.receive"); > > From my understanding, the route is consuming from zaq/avila/send, a > processor is applied and then the message is published to > zaq/avila/receive. > The to() part does not appear to be happening, when I check the console, I > see that the processor executes though no message is published to > zaq/avila/receive. Also, within the web console I see that the messages in > zaq/avila/send for enqueued and dequeued increment even when I only > pusblished one message. In addition, if I shutdown ActiveMQ I get the > following: > > INFO | Waiting as there are still 1 inflight and pending exchanges to > complete, > timeout in 7 seconds. > > Also: > > WARN | Error occurred while shutting down service: > Endpoint[mqtt://test?publish > TopicName=zaq.avila.receive]. This exception will be ignored. > java.lang.NullPointerException > > These exception make me wonder that the exchange is not completing and > something is missing. I need help! > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Java-Route-Not-Finishing-tp5747047.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
