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

[Artemis] JMS CorrelationID header in bytes format sent incorrectly when using Qpid JMS

    XMLWordPrintable

Details

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

      1. Start Artemis
      2. Send a JMS message using Qpid JMS client. Set the correlation ID by calling the setJMSCorrelationIDAsBytes() function on the message prior to sending.
      3. Receive the JMS message using Qpid JMS client. Call the function getJMSCorrelationIDAsBytes() on the received message to retrieve the correlation ID.

      Expected result:
      Original bytes correlation ID is received.

      Actual result:
      javax.jms.JMSException: The underlying correlation-id is not binary and so can't be returned
      The correlation ID can be received as a regular string using getJMSCorrelationID(), but is returned with "ID:" prepended to the original ID.

      Show
      1. Start Artemis 2. Send a JMS message using Qpid JMS client. Set the correlation ID by calling the setJMSCorrelationIDAsBytes() function on the message prior to sending. 3. Receive the JMS message using Qpid JMS client. Call the function getJMSCorrelationIDAsBytes() on the received message to retrieve the correlation ID. Expected result: Original bytes correlation ID is received. Actual result: javax.jms.JMSException: The underlying correlation-id is not binary and so can't be returned The correlation ID can be received as a regular string using getJMSCorrelationID(), but is returned with "ID:" prepended to the original ID.
    • AMQ 7.0.2 sprint 1

    Description

      When using the Qpid JMS client (AMQP 1.0), sending messages containing a JMS Correlation ID header in bytes format is sent to the consumer in string format instead with the string "ID:" prepended.

      Attachments

        1. Receiver.java
          3 kB
        2. Sender.java
          3 kB

        Issue Links

          is blocked by

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-419 Release 7.0.0.ER9 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-629 Loading...

          Activity

            People

              rh-ee-ataylor Andy Taylor
              kvanderr@redhat.com Kim van der Riet
              Dmitrii Puzikov Dmitrii Puzikov (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: