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

AMQ6 and AMQ7 compatibility: replyTo header is encoded for stomp protocol in AMQ 7.x

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • AMQ 7.3.0.GA
    • AMQ 7.2.0.GA
    • stomp-protocol
    • None
    • +
    • ARTEMIS-2311
    • Verified in a release
    • Hide
      • Unzip attachment, stomp_consumer.py is the receiver and activemq-camel-request-reply is the producer.
      • First install python stompest module. 
         pip install stompest
      • Run listener with command 
        python stomp_consumer.py
      • Now run the camel based producer. To run, first go to the location of pom.xml within project activemq-camel-request-reply and than execute 
        mvn camel:run
      • Also you would notice that correlation-id is changed as soon as consumer(python client) receive message, if we uncomment receiver part in camel based reproducer than we find that for camel as consumer and producer the correlation-id remains same.
      • This code can be checked with AMQ 6.x and AMQ 7.x with default setup and username and password of broker are set to admin.
      Show
      Unzip attachment, stomp_consumer.py is the receiver and activemq-camel-request-reply is the producer. First install python stompest module. pip install stompest Run listener with command python stomp_consumer.py Now run the camel based producer. To run, first go to the location of pom.xml within project activemq-camel-request-reply and than execute mvn camel:run Also you would notice that correlation-id is changed as soon as consumer(python client) receive message, if we uncomment receiver part in camel based reproducer than we find that for camel as consumer and producer the correlation-id remains same. This code can be checked with AMQ 6.x and AMQ 7.x with default setup and username and password of broker are set to admin.

      • One customer is migrating from AMQ 6.3 to AMQ7.x. In 6.3 he has such a setup where camel based producer send OpenWire message to 61616 port. Python based stompest client is used as Consumer which consumes messages from 61613 stomp port. It is a request-reply model.
      • Same he is setting up with AMQ 7.2(Artemis latest code base too). However, replyTo header received in python consumer client for AMQ 7.2 is not readable. Header in AMQ 7.2 is set as u'__HDR_REPLY_TO': u'[B@23f93925' while in AMQ 6.3 it is readable u'reply-to': u'/queue/pricing.quoting.dispatch.result
      • It is not smooth migration for customer.

      Complete headers for AMQ 6.3 and AMQ 7.2: 

      AMQ 6.3
{u'breadcrumbId': u'ID-chandrashekhar-45421-1554994068226-0-19', u'expires': u'0', u'timestamp': u'1554994249708', u'destination': u'/queue/pricing.quoting.dispatch.work', u'correlation-id': u'Camel-ID-chandrashekhar-45421-1554994068226-0-21', u'persistent': u'true', u'priority': u'4', u'reply-to': u'/queue/pricing.quoting.dispatch.result', u'message-id': u'ID:chandrashekhar-45475-1554994069866-1:1:2:1:7', u'firedTime': u'Thu Apr 11 20:20:49 IST 2019', u'subscription': u'0'}


AMQ 7.2
{u'content-length': u'8', u'__HDR_ARRIVAL': u'0', u'__HDR_MESSAGE_ID': u'[B@3564d4d9', u'__AMQ_CID': u'ID:chandrashekhar-42029-1554997339655-0:1', u'__HDR_REPLY_TO': u'[B@23f93925', u'__HDR_DROPPABLE': u'false', u'breadcrumbId': u'ID-chandrashekhar-33047-1554997337934-0-7', u'__HDR_PRODUCER_ID': u'[B@22fb4796', u'destination': u'pricing.quoting.dispatch.work', u'correlation-id': u'Camel-ID-chandrashekhar-33047-1554997337934-0-9', u'priority': u'4', u'redelivered': u'false', u'__HDR_BROKER_IN_TIME': u'1554997399441', u'__HDR_GROUP_SEQUENCE': u'0', u'timestamp': u'1554997399440', u'expires': u'0', u'firedTime': u'Thu Apr 11 21:13:19 IST 2019', u'__HDR_MARSHALL_PROP': u'[B@6138cc4d', u'__HDR_COMMAND_ID': u'125', u'subscription': u'0', u'destination-type': u'ANYCAST', u'persistent': u'true', u'message-id': u'1135'}

              csuconic@redhat.com Clebert Suconic
              rhn-support-cpandey Chandra Shekhar Pandey (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: