[jira] [Updated] (AMQ-5419) Disconnect between exclusive consumer documentation and functionality
[ https://issues.apache.org/jira/browse/AMQ-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james updated AMQ-5419: --- Attachment: ExclusiveConsumerNetworkTest.java So, i was trying to create a unit test that worked, so i could figure out which scenario worked and which didn't. this was my first attempt at a "basic" setup, but it doesn't seem to work reliably. occassionally it works, but usually it fails. Any suggestions on how i might be setting this up incorrectly? > Disconnect between exclusive consumer documentation and functionality > - > > Key: AMQ-5419 > URL: https://issues.apache.org/jira/browse/AMQ-5419 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.9.1 >Reporter: james >Priority: Critical > Attachments: ExclusiveConsumerNetworkTest.java > > > The ["exclusive consumer" > documentation|http://activemq.apache.org/exclusive-consumer.html] 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 > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-5419) Disconnect between exclusive consumer documentation and functionality
[ https://issues.apache.org/jira/browse/AMQ-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james updated AMQ-5419: --- Description: The ["exclusive consumer" documentation|http://activemq.apache.org/exclusive-consumer.html] 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 . was: 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 . > Disconnect between exclusive consumer documentation and functionality > - > > Key: AMQ-5419 > URL: https://issues.apache.org/jira/browse/AMQ-5419 > Project: ActiveMQ > Issue Type: Bug > Components: Documentation >Affects Versions: 5.9.1 >Reporter: james >Priority: Critical > > The ["exclusive consumer" > documentation|http://activemq.apache.org/exclusive-consumer.html] 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 > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-5419) Disconnect between exclusive consumer documentation and functionality
[ https://issues.apache.org/jira/browse/AMQ-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james updated AMQ-5419: --- 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 . was: 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. 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 . > Disconnect between exclusive consumer documentation and functionality > - > > Key: AMQ-5419 > URL: https://issues.apache.org/jira/browse/AMQ-5419 > 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: > http://activemq.2283324.n4.nabble.com/exclusive-consumer-doesn-t-seem-to-be-working-tt4686733.html > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMQ-5419) Disconnect between exclusive consumer documentation and functionality
[ https://issues.apache.org/jira/browse/AMQ-5419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] james updated AMQ-5419: --- 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 . was: 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 . > Disconnect between exclusive consumer documentation and functionality > - > > Key: AMQ-5419 > URL: https://issues.apache.org/jira/browse/AMQ-5419 > 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: > http://activemq.2283324.n4.nabble.com/exclusive-consumer-doesn-t-seem-to-be-working-tt4686733.html > . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
