If the incoming message via the MQTT consumer was InOut (i.e.
request-reply), it's likely that the JMS producer is sending the message as
InOut. This means that the producer is waiting for a reply.
Try setting the 'exchangePattern' option on the JMS endpoint to 'InOnly' to
instruct the producer that it must not wait for a reply, i.e.:
.to("jms:topic:zaq.avila.receive?exchangePattern=InOnly");
Let us know if this fixed your issue.
Thanks,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Feb 13, 2014 at 6:56 PM, Zadko <zaqavil...@gmail.com> wrote:
> It turns out that the MQTT component only supports consuming from that
> endpoint. I figured out that I can consume a message as an MQTT message if
> I
> send the message as a JMS. Like follows:
>
> from("mqtt:test?subscribeTopicName=zaq.avila.send")
> .process(new RestProcessor())
> .to("jms:topic:zaq.avila.receive");
>
> The MQTT subscriber receives the payload of the JMS message as the body of
> the mqtt message. It works very well. I'm not sure what the shorthand of
> approaching it this way are. If there are any, please let me know.
>
> Thank you for addressing my question
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Java-Route-Not-Finishing-tp5747047p5747273.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
