Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-853

[A-MQ7, Core client] Core client should be notified if consumer is closed on broker side

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • None
    • core-protocol
    • None
    • Hide
      1. Start broker
      2. Create address named Test
      3. Create address named Test
      4. Start core client and connect to broker as receiver using e.g. following command: 
        java -jar /var/dtests/node_data/clients/acce.jar receiver --timeout 3600 --log-msgs dict --broker "localhost:61616" --conn-username admin --conn-password admin --address "Test" --count 20
      5. Kill consumer (representation of this client on broker's side), e.g. using Hawtio console (see attached screenshot)
      6. Try to send messages to given queue -> client wont receive any.
      Show
      Start broker Create address named Test Create address named Test Start core client and connect to broker as receiver using e.g. following command: java -jar /var/dtests/node_data/clients/acce.jar receiver --timeout 3600 --log-msgs dict --broker "localhost:61616" --conn-username admin --conn-password admin --address "Test" --count 20 Kill consumer (representation of this client on broker's side), e.g. using Hawtio console (see attached screenshot) Try to send messages to given queue -> client wont receive any.

    Description

      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.

      Attachments

        Issue Links

          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-837 [A-MQ7, Hawtio] Client does not recieve any info about AMQP session being killed

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-854 [A-MQ7, Hawtio] Close button in Sessions tab and Consumers tab may be confusing in what it actually does

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rvais Roman Vais
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: