Inline...
On Tue, Apr 30, 2013 at 2:42 AM, marnold <malcolmarn...@gmail.com> wrote: > Thanks Christian. > > (I work with Deepak.) > > In our system, Camel produces JMS messages from integrated endpoints, which > are consumed by EJB MDBs. The EJB application 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. > So if you're communicating with the broker using transactions, everything except the commit/rollback will be sent asynchronous. This could lead to blocking the entire connection on producer flow control. Try setting the producer window on your connections as described in http://activemq.apache.org/producer-flow-control.html > > Our Camel process has a single Spring bean for the ActiveMQ broker > (org.apache.activemq.camel.component.ActiveMQComponent), so I assume this > means it both consumes and produces on the same connection? > Mmmm.. depends on how you configured your connection factory... are you pooling connections? > > In the Camel documentation, I can see that JMS property asyncConsumer is > default 'false'. But there does not seem to be a property 'asyncProducer'? > Well... I think those properties are more for how the endpoint treats the exchange with regard to ordering and async processing > > Would the best way to resolve this - in our case - to ensure Camel is a > synchronous producer, or to ensure Camel uses one connection to produce > messages and a different connection to consume messages? > > Try setting the producer window on your connection so that PFC doesn't block the entire connection. > Thanks in advance. > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Query-around-ActiveMQ-DLQ-tp4666277p4666444.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
