Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-9248

Exception is thrown when receiving a message where JMSDestination is null

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.16.0
    • 2.16.1, 2.17.0
    • camel-jms
    • None
    • Unknown
    • Regression

    Description

      The change linked below causes camel-jms throws an exception when a message is received where JMSDestination is null (when used with WebSphere MQ).
      This works as expected in 2.15.3.

      The message looks like this (anonymized)
      JMSMessage class: jms_text
      JMSType: null
      JMSDeliveryMode: 2
      JMSExpiration: 0
      JMSPriority: 5
      JMSMessageID: ID:c3e2d840e3d4d8d44040404040404040cfbd668a5f4f4261
      JMSTimestamp: 1445609217800
      JMSCorrelationID: null
      JMSDestination: null
      JMSReplyTo: queue://TEST/INPUT.QUEUE?targetClient=1
      JMSRedelivered: false
      JMSXAppID: ilities\RFHUtil\rfhutilc.exe
      JMSXDeliveryCount: 1
      JMSXUserID: MQXPLO
      JMS_IBM_Character_Set: IBM277
      JMS_IBM_Encoding: 785
      JMS_IBM_Format: MQSTR
      JMS_IBM_MsgType: 8
      JMS_IBM_PutApplType: 11
      JMS_IBM_PutDate: 20151023
      JMS_IBM_PutTime: 14065780

      The following is a link to the troublesome patch included in 2.16.0:
      https://fisheye6.atlassian.com/browse/camel-git/components/camel-jms/src/main/java/org/apache/camel/component/jms/EndpointMessageListener.java?r2=812fa060bfeac5b320624b5d6d4833ac441d42c9&r1=e00e0d6599b01733c270f3053e23118d35ea0881

      Attachments

        Issue Links

          Activity

            People

              davsclaus Claus Ibsen
              jinie Jimmy Selgen Nielsen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: