-
Story
-
Resolution: Unresolved
-
Major
-
None
-
AMQ 7.0.3.GA
-
None
-
None
-
Documentation (Ref Guide, User Guide, etc.), User Experience
If sessions of receiver client are remotely killed, client is not notified about the fact and it is still running but cannot receive any messages. If it is done via new feature of hawtio console, page won't refresh after confirming dialog that you want to kill selected session.
The same applies when receiver client is killed as "consumer" - sessions and connection are still alive, but client cannot receive any mesages sent.
Behavior described above may be confusing to the customers. This kind of notification should work for Core protocol, but doesn't for AMQP and Open Wire. There for we suggest to implement some sort of notification for other protocols as well.
- is related to
-
ENTMQBR-698 [A-MQ7, JMX management] console tree view of clients connections / sessions / producers / consumer
- Closed
- relates to
-
ENTMQBR-853 [A-MQ7, Core client] Core client should be notified if consumer is closed on broker side
- New
-
ENTMQBR-854 [A-MQ7, Hawtio] Close button in Sessions tab and Consumers tab may be confusing in what it actually does
- Closed