[
https://issues.apache.org/jira/browse/ARTEMIS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114313#comment-15114313
]
ASF GitHub Bot commented on ARTEMIS-358:
----------------------------------------
GitHub user scop opened a pull request:
https://github.com/apache/activemq-artemis/pull/341
ARTEMIS-358 test case for topic disappearing on disconnect without unsub
Test case (not a fix) demonstrating the issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scop/activemq-artemis topic-disappears
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/341.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #341
----
commit c84f9c644c15cafeb02526c9343c17d538cdade9
Author: Ville Skyttä <ville.sky...@iki.fi>
Date: 2016-01-24T13:50:53Z
ARTEMIS-358 test case for topic disappearing on disconnect without
unsubscribe
----
> Topic disappears when STOMP subscriber client disconnects without unsubscribe
> -----------------------------------------------------------------------------
>
> Key: ARTEMIS-358
> URL: https://issues.apache.org/jira/browse/ARTEMIS-358
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Ville Skyttä
>
> When a STOMP client which has a subscription to a topic disconnects without
> unsubscribing first, the topic seems to disappear.
> Reproducer:
> # configure a server with a topic (e.g. jms.topic.testtopic) and start it
> # STOMP: connect to the server
> # STOMP: subscribe to the topic
> # STOMP: disconnect from the server (without unsubscribing first)
> # STOMP: connect to the server again
> # STOMP: send a message to the topic
> At this point the server responds with "AMQ339001: Destination does not
> exist: jms.topic.testtopic"
> At this point the topic is still visible in jconsole though so maybe it has
> not disappeared entirely, but anyway, messages cannot be sent to it with
> STOMP any more. Restarting the server makes it possible to send to it again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
