activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-3917) ActiveMQ should support multiple durable subscriptions per Stomp client
Date Fri, 27 Jul 2012 12:44:34 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


View raw message