Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of christian.posta@gmail.com
 designates 209.85.217.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1367314963256-4666444.post@n4.nabble.com>
References: <1366999937865-4666277.post@n4.nabble.com>
	<CAKS7T5ONQ-3=2oj5RXHPao1_Q3_U7oe_dH_u7FgjdSJhB=pELQ@mail.gmail.com>
	<1367055856989-4666305.post@n4.nabble.com>
	<1367258922594-4666406.post@n4.nabble.com>
	<CAKS7T5OjSerX8y9d4JHHbYE_CyPez1LNvavcLBRcoHNA71Re0Q@mail.gmail.com>
	<1367314963256-4666444.post@n4.nabble.com>
Date: Tue, 30 Apr 2013 07:41:30 -0700
Message-ID: 
 <CAKS7T5O7ejcRPKt3p4h3dSu-Wen=mnC1PmxA1bpd5rT4JDuCJw@mail.gmail.com>
Subject: Re: Query around ActiveMQ.DLQ
From: Christian Posta <christian.posta@gmail.com>
To: "users@activemq.apache.org" <users@activemq.apache.org>
Content-Type: multipart/alternative; boundary=001a11c237c43be82304db94ffb3

--001a11c237c43be82304db94ffb3
Content-Type: text/plain; charset=ISO-8859-1

Inline...


On Tue, Apr 30, 2013 at 2:42 AM, marnold <malcolmarnold@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

--001a11c237c43be82304db94ffb3--