You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Zemian Deng (JIRA)" <ji...@apache.org> on 2013/08/07 01:49:47 UTC
[jira] [Commented] (CAMEL-6093) 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.
[ https://issues.apache.org/jira/browse/CAMEL-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731458#comment-13731458 ]
Zemian Deng commented on CAMEL-6093:
------------------------------------
Hi,
I have looked at this issue, and it appeared that simple fix is to make JmsEndpoint#isSingle() to return false for both Queue and Topic cases. But if we do this, we will not able to manage the Queue endpoint through JMX because in DefaultManagementObjectStrategy#getManagedObjectForEndpoint() it will return null for non-singleton endpoint. Is this intended? If yes, what's a suggested solution for it? I will be happy to help come up with a patch if you guys can give some advise here.
Zemian
> 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
> Reporter: Ladislav Lengyel
> Assignee: Claus Ibsen
> 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