[
https://issues.apache.org/jira/browse/AMQ-5622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343357#comment-14343357
]
Michael Justin commented on AMQ-5622:
-------------------------------------
It works as expected but only with STOMP 1.1 (in my client library).
If I modify the ActiveMQ test Stomp11Test.testDurableSubAndUnSubOnTwoTopics to
use STOMP 1.2 it fails to find the subscription ("test1"):
String connectFrame = "STOMP\n" +
"login:system\n" + "passcode:manager\n" +
"accept-version:1.2\n" +
"host:localhost\n" + "client-id:test\n" + "\n" + Stomp.NULL;
2015-03-02 17:37:11,730 [0.1:49541@49534] - WARN ProtocolConverter
- Exception occurred processing:
UNSUBSCRIBE
activemq.subscriptionName:test1
receipt:3
destination:/topic/org.apache.activemq.transport.stomp.Stomp11Test.testDurableSubAndUnSubOnTwoTopics1
id:durablesub-1
It should work in the same way with both protocol versions (1.1 and 1.2) if I
understand the 1.2 protocol changes correctly
> STOMP clients can only delete durable subscriptions when clientId equals
> subscriptionName
> -----------------------------------------------------------------------------------------
>
> Key: AMQ-5622
> URL: https://issues.apache.org/jira/browse/AMQ-5622
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.7.0
> Reporter: Michael Justin
> Labels: test
>
> For durable topic subscriptions STOMP clients must specify the same clientId
> on the connection and subcriptionName on the subscribe prior to v5.7.0.
> (https://issues.apache.org/jira/browse/AMQ-3917)
> Removing the subscription however is only possible if the same clientId on
> the connection and subcriptionName on the subscribe is used. The STOMP unit
> tests fulfill this condition (both have the same value, "test"). I suggest to
> modify the unit test to use different values for clientId and subcriptionName
> to verify this bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
