activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-5419) Disconnect between exclusive consumer documentation and functionality
Date Mon, 03 Nov 2014 14:59:33 GMT


Timothy Bish commented on AMQ-5419:

Please add a junit test case to demonstrate you problem, and also a link to the documentation
in question.  

> Disconnect between exclusive consumer documentation and functionality
> ---------------------------------------------------------------------
>                 Key: AMQ-5419
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 5.9.1
>            Reporter: james
>            Priority: Critical
> 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:

This message was sent by Atlassian JIRA

View raw message