You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@camel.apache.org by thulasi <th...@gmail.com> on 2017/05/24 12:50:55 UTC

Two Camel Configs Polling Same IBM MQ. Only one picking the message

hi,

i have two camel applications running in 2 different VM's, both the
applications are polling same MQ to pull the requests.

when i try to run one application at a time, each application is reading
messages without any issue(when only application is running)

when i try running both application at the same time, only one application
is reading messages and the other is idle. even tough MQ is having 50
messages.

only one application is reading all the messages by creating 50 threads.

can some tell me how can i make both applications pick the messages.




--
View this message in context: http://camel.465427.n5.nabble.com/Two-Camel-Configs-Polling-Same-IBM-MQ-Only-one-picking-the-message-tp5800355.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Two Camel Configs Polling Same IBM MQ. Only one picking the message

Posted by clinton <cl...@ionep.com>.

There is a property on the queue itself inside of MQ, that can control this. 
Called Default ReadAhead.  Set to "disabled"



--
View this message in context: http://camel.465427.n5.nabble.com/Two-Camel-Configs-Polling-Same-IBM-MQ-Only-one-picking-the-message-tp5800355p5800405.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Two Camel Configs Polling Same IBM MQ. Only one picking the message

Posted by thulasi <th...@gmail.com>.

thanks for the reply.

can you please send the property which needs to be configured.



--
View this message in context: http://camel.465427.n5.nabble.com/Two-Camel-Configs-Polling-Same-IBM-MQ-Only-one-picking-the-message-tp5800355p5800368.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Two Camel Configs Polling Same IBM MQ. Only one picking the message

Posted by clinton <cl...@ionep.com>.

I think you have some "read ahead" (prefetching) going on.  I've seen that
happening such that a consumer doesn't just read "the next" msg, but reads
in a bunch and holds them for the consuming process.  You should be able to
limit that behavior with a property setting.




--
View this message in context: http://camel.465427.n5.nabble.com/Two-Camel-Configs-Polling-Same-IBM-MQ-Only-one-picking-the-message-tp5800355p5800367.html
Sent from the Camel - Users mailing list archive at Nabble.com.