Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Abandoned
-
5.9.1
-
None
-
None
Description
The "exclusive consumer" documentation seems indicates that this feature is enabled for a given consumer. In practice, however, the feature seems to be tied to the connection as well as the consumer. If a consumer with the "exclusive" flag enabled is created using a connection without the "exclusive" flag enabled, the consumer will behave like a normal consumer. The exclusive feature will only work if the connection associated with the consumer also has the "exclusive" flag enabled. I marked this as a "documentation" bug, but it's possible that the documentation is the intended behavior and there is actually a code problem?
See this thread for more details on my exploration of this feature: http://activemq.2283324.n4.nabble.com/exclusive-consumer-doesn-t-seem-to-be-working-tt4686733.html .