camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raul Kripalani (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5865) camel-jms: concurrent consumers on Temp Reply Queue requires more work
Date Wed, 09 Jan 2013 23:56:14 GMT


Raul Kripalani commented on CAMEL-5865:

Also added logic to refresh the ReplyTo destination if the underlying connection fails.
> camel-jms: concurrent consumers on Temp Reply Queue requires more work
> ----------------------------------------------------------------------
>                 Key: CAMEL-5865
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.10.3
>            Reporter: Raul Kripalani
>            Assignee: Raul Kripalani
>             Fix For: 2.10.4, 2.11.0
> This feature requires a bit more work to get right. Currently it's a bit buggy. Here
are the reasons:
> - every time the DLMC initialises a new consumer task (AsyncMessageListenerInvoker),
it invokes the Destination Resolver. The current code ends up creating a new temp queue and
overwriting the reply queue in the Reply Manager every time.
> - temp queues can only be consumed from by the same JMS connection that created the queue.
If you use a connection pool and maxConsumers > 1, there's no way to guarantee that the
same JMS connection is used to create the subsequent consumers, as concurrency expands. We
should explicitly set cacheLevel=CACHE_CONSUMER which activates sharing the connection in
the DLMC across consumers.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message