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

broker does not set message ID header on cross protocol consumption

    XMLWordPrintable

Details

    • +
    • Hide
      Previously, when a message was received by a client using a different protocol than the one used to send it, the broker set the message ID to a null value. This issue is now resolved. A non-null message ID is always present on a received message, regardless of the protocols used to send and receive the message.
      Show
      Previously, when a message was received by a client using a different protocol than the one used to send it, the broker set the message ID to a null value. This issue is now resolved. A non-null message ID is always present on a received message, regardless of the protocols used to send and receive the message.
    • Documented as Resolved Issue
    • Verified in a release
    • Hide

      Use the "./bin/artemis producer" to produce some messages. Use any client based on Qpid JMS (I can provide one if necessary) and note that the JMS Message ID is null.

      Show
      Use the "./bin/artemis producer" to produce some messages. Use any client based on Qpid JMS (I can provide one if necessary) and note that the JMS Message ID is null.
    • AMQ Broker 2619, AMQ Broker 2919, ignore

    Description

      A client that uses Core-JMS, Qpid JMS, or OpenWire sets the JMSMessageID header automatically. A Core-JMS or OpenWire client will retrieve that header in a call to

      Message.getJMSMessageID()

      However, a Qpid JMS client will only retrieve a non-null value for the JMS Message ID if the message was produced by a Qpid JMS client. If the message was produced using a Core-JMS or OpenWire client, the Qpid JMS client reads the message ID as null.

      Attachments

        Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-569 Conversion of IDs from Openwire to AMQP results in sending IDs as binary

          • 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
          links to

          Web Link PR

          Activity

            People

              gaohoward Howard Gao
              rhn-support-kboone Kevin Boone
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: