[
https://issues.apache.org/jira/browse/ARTEMIS-1486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16237458#comment-16237458
]
ASF GitHub Bot commented on ARTEMIS-1486:
-----------------------------------------
GitHub user stanlyDoge opened a pull request:
https://github.com/apache/activemq-artemis/pull/1635
ARTEMIS-1486 Clean up client disconnecting tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stanlyDoge/activemq-artemis-1 chngs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/1635.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 #1635
----
commit e8bc60ee003213dd90369cf6786190ae1dc24326
Author: Stanislav Knot <[email protected]>
Date: 2017-10-31T13:08:23Z
ARTEMIS-1486 Core client should be notified if consumer is closed on broker
side
commit c0ac1836dc8f851c293a41838db2555946dc5047
Author: Stanislav Knot <[email protected]>
Date: 2017-11-02T17:11:29Z
ARTEMIS-1486 added JMS client test
----
> Core client should be notified if consumer is closed on broker side
> -------------------------------------------------------------------
>
> Key: ARTEMIS-1486
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1486
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Stanislav Knot
> Priority: Major
>
> If consumer is closed on broker using e.g. Hawtio console, client connected
> as that consumer (representation of broker resource) should be notified about
> that fact and react to that. It doesn't seem to react. If consumer is closed,
> as a result of not being notified, client hangs in the air and cannot receive
> messages.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
