Hi,

In our system, Camel produces JMS messages from integrated endpoints, which
are consumed by EJB MDBs.  
The EJB application in-turn produces new JMS messages, which are consumed by
Camel to send to other integrated endpoints (eg. WebSphere MQ).  
We use transacted routes, and Atomikos as XA transaction coordinator. 
ActiveMQ 5.6.0, Camel 2.9.0. 

At most only one Queue can be mapped to a single EJB MDB.

So effectively each EJB consumes messages from a Queue - to which multiple
camel routes (publishers) have published messages.

I want to ensure that each producer(s) have the same level of priority in
publishing to the Queue.
i.e. Assume - I have 3 producers, I don't want a scenario where Producer 1
and Producer 2 publish 1000 messages each followed by Producer 3. This will
result in the EJB MDB consuming messages produced by Producer 3 only after
previous 2000 messages.

Is setting the PrefetchPolicy to 1 (or something not high enough) in all the
Producers - the right approach to tackle this?
i.e. this way I ensure that each producer has the same opportunity to send a
definite number of messages to the Queue.


regards
D



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Multiple-Producers-one-consumer-use-of-PrefetchPolicy-tp4666895.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Reply via email to