[
https://issues.apache.org/jira/browse/CAMEL-6093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13754638#comment-13754638
]
Claus Ibsen commented on CAMEL-6093:
------------------------------------
I wonder if the best solution is to let JmsEndpoint not be singleton so its not
shared at all. And then introduce a new option on Endpoint to indicate that it
should be enlisted in JMX, even if its not singleton. The trick is that you may
have JmsEndpoints in JMX that would have the same ObjectName but would be
different instances. To make the MBean names unique we would need to add the
identity hashcode of the endpoint instance to the MBean name which then makes
them look a bit ugly
"jms:queue:foo(0x12de45)"
"jms:queue:foo(0x0a1348)"
> 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
> Fix For: 2.10.7, 2.11.2, 2.12.1
>
> 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
