You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bhanu (JIRA)" <ji...@apache.org> on 2012/07/09 10:57:35 UTC
[jira] [Created] (AMQ-3917) ActiveMQ should support multiple
durable subscriptions per Stomp client
Bhanu created AMQ-3917:
--------------------------
Summary: ActiveMQ should support multiple durable subscriptions per Stomp client
Key: AMQ-3917
URL: https://issues.apache.org/jira/browse/AMQ-3917
Project: ActiveMQ
Issue Type: Bug
Components: Broker, stomp
Affects Versions: 5.6.0, 5.5.1
Environment: linux, solaris
Reporter: Bhanu
This is coming from AMQ-3802.
Quoting Timothy - "This is another limitation of the Stomp support which allows for only one durable subscription since clientId and subscription name are linked. This is because the Stomp v1.0 spec didn't require that you assign unique Ids to subscriptions, so the correlation is made per connection using the matching clientId and subscription name. You can work around this by creating a connection for each durable subscriber."
Now, since ActiveMQ v5.6.0 supports Stomp v1.1 which has made the id header mandatory for subscribe and unsubscribe calls, we should leverage this feature and allow for multiple durable subscriptions per stomp client. Hacks like creating a separate connection for each durable subscriber should be avoided.
Let me know if you have any queries?
Thanks,
Bhanu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQ-3917) ActiveMQ should support multiple
durable subscriptions per Stomp client
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQ-3917:
------------------------------
Priority: Minor (was: Major)
Issue Type: New Feature (was: Bug)
> ActiveMQ should support multiple durable subscriptions per Stomp client
> -----------------------------------------------------------------------
>
> Key: AMQ-3917
> URL: https://issues.apache.org/jira/browse/AMQ-3917
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, stomp
> Affects Versions: 5.5.1, 5.6.0
> Environment: linux, solaris
> Reporter: Bhanu
> Priority: Minor
>
> This is coming from AMQ-3802.
> Quoting Timothy - "This is another limitation of the Stomp support which allows for only one durable subscription since clientId and subscription name are linked. This is because the Stomp v1.0 spec didn't require that you assign unique Ids to subscriptions, so the correlation is made per connection using the matching clientId and subscription name. You can work around this by creating a connection for each durable subscriber."
> Now, since ActiveMQ v5.6.0 supports Stomp v1.1 which has made the id header mandatory for subscribe and unsubscribe calls, we should leverage this feature and allow for multiple durable subscriptions per stomp client. Hacks like creating a separate connection for each durable subscriber should be avoided.
> Let me know if you have any queries?
> Thanks,
> Bhanu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3917) ActiveMQ should support multiple
durable subscriptions per Stomp client
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423845#comment-13423845 ]
Timothy Bish commented on AMQ-3917:
-----------------------------------
Have a look at the Stomp v1.1 unit tests it shows what you need to do, basically it works like the JMS side, you need a client-id that is used each time you connect and each subscription needs to supply a subscription name that uniquely identifies that sub.
> ActiveMQ should support multiple durable subscriptions per Stomp client
> -----------------------------------------------------------------------
>
> Key: AMQ-3917
> URL: https://issues.apache.org/jira/browse/AMQ-3917
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, stomp
> Affects Versions: 5.5.1, 5.6.0
> Environment: linux, solaris
> Reporter: Bhanu
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.7.0
>
>
> This is coming from AMQ-3802.
> Quoting Timothy - "This is another limitation of the Stomp support which allows for only one durable subscription since clientId and subscription name are linked. This is because the Stomp v1.0 spec didn't require that you assign unique Ids to subscriptions, so the correlation is made per connection using the matching clientId and subscription name. You can work around this by creating a connection for each durable subscriber."
> Now, since ActiveMQ v5.6.0 supports Stomp v1.1 which has made the id header mandatory for subscribe and unsubscribe calls, we should leverage this feature and allow for multiple durable subscriptions per stomp client. Hacks like creating a separate connection for each durable subscriber should be avoided.
> Let me know if you have any queries?
> Thanks,
> Bhanu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3917) ActiveMQ should support multiple
durable subscriptions per Stomp client
Posted by "Buchi Reddy B (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13423701#comment-13423701 ]
Buchi Reddy B commented on AMQ-3917:
------------------------------------
@Timothy Can you please give some overview how you fixed this? Do you use the 'id' itself to identify a subscription uniquely? Is 'activemq.subscriptionName' header still there or is it removed?
We have some hacks in our code and getting more understanding of your fix would help us remove those hacks when we move to ActiveMQ 5.7.0.
Thanks in advance!!
> ActiveMQ should support multiple durable subscriptions per Stomp client
> -----------------------------------------------------------------------
>
> Key: AMQ-3917
> URL: https://issues.apache.org/jira/browse/AMQ-3917
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, stomp
> Affects Versions: 5.5.1, 5.6.0
> Environment: linux, solaris
> Reporter: Bhanu
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.7.0
>
>
> This is coming from AMQ-3802.
> Quoting Timothy - "This is another limitation of the Stomp support which allows for only one durable subscription since clientId and subscription name are linked. This is because the Stomp v1.0 spec didn't require that you assign unique Ids to subscriptions, so the correlation is made per connection using the matching clientId and subscription name. You can work around this by creating a connection for each durable subscriber."
> Now, since ActiveMQ v5.6.0 supports Stomp v1.1 which has made the id header mandatory for subscribe and unsubscribe calls, we should leverage this feature and allow for multiple durable subscriptions per stomp client. Hacks like creating a separate connection for each durable subscriber should be avoided.
> Let me know if you have any queries?
> Thanks,
> Bhanu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-3917) ActiveMQ should support multiple
durable subscriptions per Stomp client
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQ-3917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-3917.
-------------------------------
Resolution: Fixed
Fix Version/s: 5.7.0
Assignee: Timothy Bish
Fixed in trunk.
> ActiveMQ should support multiple durable subscriptions per Stomp client
> -----------------------------------------------------------------------
>
> Key: AMQ-3917
> URL: https://issues.apache.org/jira/browse/AMQ-3917
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, stomp
> Affects Versions: 5.5.1, 5.6.0
> Environment: linux, solaris
> Reporter: Bhanu
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.7.0
>
>
> This is coming from AMQ-3802.
> Quoting Timothy - "This is another limitation of the Stomp support which allows for only one durable subscription since clientId and subscription name are linked. This is because the Stomp v1.0 spec didn't require that you assign unique Ids to subscriptions, so the correlation is made per connection using the matching clientId and subscription name. You can work around this by creating a connection for each durable subscriber."
> Now, since ActiveMQ v5.6.0 supports Stomp v1.1 which has made the id header mandatory for subscribe and unsubscribe calls, we should leverage this feature and allow for multiple durable subscriptions per stomp client. Hacks like creating a separate connection for each durable subscriber should be avoided.
> Let me know if you have any queries?
> Thanks,
> Bhanu
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira