You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Evan Hecht (JIRA)" <ji...@apache.org> on 2008/08/28 01:33:52 UTC
[jira] Created: (AMQ-1915)
ActiveMQConnectionFactory.setExclusiveConsumer has no effect
ActiveMQConnectionFactory.setExclusiveConsumer has no effect
------------------------------------------------------------
Key: AMQ-1915
URL: https://issues.apache.org/activemq/browse/AMQ-1915
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.1.0
Environment: (irrelevant) Windows XP
Reporter: Evan Hecht
Priority: Minor
Creating an {{ActiveMQConnectionFactory}}, and then calling {{setExclusiveConsumer(true)}}, does *not* cause queues created from that factory's connections to have the exclusive consumer feature. I'm pretty sure this is due to {{configureConnection()}} not calling {{setExclusiveConsumer()}} on new connections. This can be seen in the source code for {{ActiveMQConnectionFactory.configureConnection}}, release 5.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1915)
ActiveMQConnectionFactory.setExclusiveConsumer has no effect
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1915:
-------------------------------
Assignee: Rob Davies
> ActiveMQConnectionFactory.setExclusiveConsumer has no effect
> ------------------------------------------------------------
>
> Key: AMQ-1915
> URL: https://issues.apache.org/activemq/browse/AMQ-1915
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Environment: (irrelevant) Windows XP
> Reporter: Evan Hecht
> Assignee: Rob Davies
> Priority: Minor
> Original Estimate: 2 minutes
> Remaining Estimate: 2 minutes
>
> Creating an {{ActiveMQConnectionFactory}}, and then calling {{setExclusiveConsumer(true)}}, does *not* cause queues created from that factory's connections to have the exclusive consumer feature. I'm pretty sure this is due to {{configureConnection()}} not calling {{setExclusiveConsumer()}} on new connections. This can be seen in the source code for {{ActiveMQConnectionFactory.configureConnection}}, release 5.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1915)
ActiveMQConnectionFactory.setExclusiveConsumer has no effect
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1915.
-----------------------------
Fix Version/s: 5.2.0
Resolution: Fixed
Fixed by SVN revision 691130
> ActiveMQConnectionFactory.setExclusiveConsumer has no effect
> ------------------------------------------------------------
>
> Key: AMQ-1915
> URL: https://issues.apache.org/activemq/browse/AMQ-1915
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.1.0
> Environment: (irrelevant) Windows XP
> Reporter: Evan Hecht
> Assignee: Rob Davies
> Priority: Minor
> Fix For: 5.2.0
>
> Original Estimate: 2 minutes
> Remaining Estimate: 2 minutes
>
> Creating an {{ActiveMQConnectionFactory}}, and then calling {{setExclusiveConsumer(true)}}, does *not* cause queues created from that factory's connections to have the exclusive consumer feature. I'm pretty sure this is due to {{configureConnection()}} not calling {{setExclusiveConsumer()}} on new connections. This can be seen in the source code for {{ActiveMQConnectionFactory.configureConnection}}, release 5.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.