[
https://issues.apache.org/jira/browse/CAMEL-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750656#comment-13750656
]
Zemian Deng commented on CAMEL-6093:
------------------------------------
Hi Christian,
I don't see how this issue is related to ActiveMQ specific. The problem I see
is that we allowing Queue to be singleton JmsEndpoint, and thus we are only
creating one threadpool service for jmsMessageListenerContainer. Thus when user
remove one consumer, the single threadpool will shutdown, and thus other active
consumers who share same single Endpoint will not receive message anymore.
If we do intended for Queue to be non-singleton as JmsEndpoint with same URI
string, then, I said, the fix is simply make JmsEndpoint#isSingle() to return
false. The only drawback now is that once you do this, you will not able to see
Queue stats through JMX because we don't expose non-single Endpoints on JMX
(there is a unit test case that verify this)
Please let me know if my diagnosis is incorrect.
> Multiple consumers exists on the same JMS endpoint uri and if you remove a
> consumer the other active consumers do not receive any messages anymore.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-6093
> URL: https://issues.apache.org/jira/browse/CAMEL-6093
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.10.3, 2.11.1
> Reporter: Ladislav Lengyel
> Assignee: Claus Ibsen
> Priority: Critical
> Fix For: 2.10.7, 2.11.2, 2.12.0
>
> Attachments: TwoConsumerOnTheSameQueueTest.java
>
>
> same issue as CAMEL-4194, but here it is for queues.
> https://issues.apache.org/jira/browse/CAMEL-4194
> description and unit test for reproduction
> http://camel.465427.n5.nabble.com/Removing-routes-programmatically-td4556741.html#a5727523
> see post on Feb 13, 2013; 4:41pm
> thanks
--
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: http://www.atlassian.com/software/jira
