You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/07/26 21:46:35 UTC
[jira] [Resolved] (AMQ-3917) ActiveMQ should support multiple
durable subscriptions per Stomp client
[ 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