[ 
https://issues.apache.org/jira/browse/CAMEL-7449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang resolved CAMEL-7449.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.14.0
                   2.13.2
                   2.12.4

Now camel can check the NPE if the JMSXUserID is not set in the JMS message.

> Camel Subscribing to messages published by non-camel producers
> --------------------------------------------------------------
>
>                 Key: CAMEL-7449
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7449
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.13.0
>         Environment: Redhat Linux
>            Reporter: James Greenwood
>            Assignee: Willem Jiang
>             Fix For: 2.12.4, 2.13.2, 2.14.0
>
>
> I have come across an issue with Camel 2.13 when subscribing to a qpid 
> messages published by a non-camel producers. The error happens with both Qpid 
> C++ producer and also a python producer. 
> An Null pointer exception is thrown in the JmsBinding.extractHeadersFromJMS 
> on line 173. 
> map.put("JMSXUserID", jmsMessage.getStringProperty("JMSXUserID")); 
> JMSXUserID has not been set by the publisher as it is a non-JMS publisher. 
> java.lang.NullPointerException
> at java.lang.String.<init>(String.java:593)
> at 
> org.apache.qpid.client.message.AMQMessageDelegate_0_10.getStringProperty(AMQMessageDelegate_0_10.java:735)
> at 
> org.apache.qpid.client.message.AbstractJMSMessage.getStringProperty(AbstractJMSMessage.java.225)
> at 
> org.apache.camel.component.jms.JmsBinding.extractHeadersFromJms(JmsBinding.java:173)
> at 
> org.apache.camel.component.jms.JmsMessage.populateInitialHeaders(JmsMessage.java:222)
> Full stack trace not show as it is on a different system
> I can see a change was made to JmsBinding.java in Camel 2.12.2 to fix a 
> ActiveMQ issue. This is what has caused the issue. The system is being 
> upgraded from Camel 2.9.2 to Camel 2.13.1 and this issue has been experienced.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to