Thanks for the information. I assume you set a camel route to send the
messages from the queue to a bean and this bean makes a client connection to
MQ? Or are these beans running outside of the Active MQ/Camel environment,
such as a Spring message driven bean?
Thanks,
Craig
sweenma wrote:
>
If you want to concurrently consume from ActiveMQ (or any JMS) with
Camel, just set the concurrentConsumers property on the URI (or
configure the component/endpoint).
See
http://camel.apache.org/jms.html
Note that concurrent consumers break order of messages on a queue. To
fix this using ActiveMQ
"Did you ever resolve this issue? I have having the same problem."
No I did not. Instead of using activemq to websphere mq communication, I
just created some reader threads that read the activemq msg's and forwarded
it off mq. Very fast.
--
View this message in context:
http://old.nabble.com/A
Did you ever resolve this issue? I have having the same problem.
Thanks,
Craig
--
View this message in context:
http://old.nabble.com/ActiveMQ-to-Websphere-MQ-tp28097168p29433806.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
