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

amqp proton clients cannot receive messages

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • A-MQ 7.0.0.ER5
    • A-MQ 7.0.0.GA
    • None
    • Hide

      1. start A-MQ7 ER4
      2. send one message to a jms.queue.test
      3. check the number of messages (1 message, expected)
      4. try to receive a message from the jms.queue.test
      5. no messages consumed (transfer did not happen); client seems to be hanged; kill the client
      6. check the messages count on jms.queue.test (2 messages, not expected)

      Show
      1. start A-MQ7 ER4 2. send one message to a jms.queue.test 3. check the number of messages (1 message, expected) 4. try to receive a message from the jms.queue.test 5. no messages consumed (transfer did not happen); client seems to be hanged; kill the client 6. check the messages count on jms.queue.test (2 messages, not expected)

    Description

      There is a regression between ER3 and ER4 builds. Proton clients cannot receive messages from the broker. This affects following supported clients: qpic-cpp legacy client, Proton c++ reactive client and Proton python reactive client.

      On ER3 build the behaviour was not ideal as well. The client could send and receive a text message but the client gets stuck afterwards (after transfer is done). The message is removed from the queue on the broker.

      On ER4 the the behaviour is similar but different. The client can send but can not receive the message. The client get stuck earlier (before the transfer is done). It seems that the message is acquired but not accepted so returned to the broker queue. In results there are most probably two duplicate messages on the broker queue.

      This is most probably related to ENTMQ-1573.

      Attachments

        1. cpp_er3.log
          9 kB
        2. cpp_er4.log
          8 kB
        3. python_er3_broker.log
          7 kB
        4. python_er3.log
          14 kB
        5. python_er4_broker.log
          9 kB
        6. python_er4.log
          13 kB

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-385 Release 7.0.0.ER5 with Hand Off document

          • 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
          is caused by

          ARTEMIS-511 Loading...

          Activity

            People

              rh-ee-ataylor Andy Taylor
              pematous Petr Matousek
              Petr Matousek Petr Matousek
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: