Exclusive Consumers is designed to work that way. If you have very high load and message spooling to disk you may be seeing some duplicate message delivery. Some issues around occasional duplicate delivery were addresses on trunk over the past few months. The current 5.3-SNAPSHOT should behave better in this regard with the caveat that Stomp was not a prerequisite for the behavior. If your test scenario does not work as expected with a 5.3-SNAPSHOT please raise a jira issue with a test case so we can attempt to address the issue for the 5.3 release.
2009/7/15 RakeshRay <rakesh....@proquest.com>: > > Starting multiple consumer using Stomp protocol, in exclusive mode kills > others and just keeps one consumerr alive. > How do I get unique messages using multiple consumers? > > If I turn off exclusive mode, and run multiple consumers they seems to get > the same message 1% off time. > > Any suggestions are welcomed! > Using active mq 5.2 > -- > View this message in context: > http://www.nabble.com/Multiple-consumer-in-exclusive-mode-does-not-work.-tp24506735p24506735.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > -- http://blog.garytully.com Open Source Integration http://fusesource.com
