camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derek Wilhelm (JIRA)" <>
Subject [jira] [Commented] (CAMEL-11772) Sjms with Artemis causes NullPointerException due to a ClassCastException
Date Tue, 12 Sep 2017 15:18:00 GMT


Derek Wilhelm commented on CAMEL-11772:

I updated the PR to include a check if the getDestinationAsString method returns null in both
camel-sjms and camel-jms.  camel-sjms2 looks like it uses camel-sjms for this piece so it
should be covered by the fix to camel-sjms.

> Sjms with Artemis causes NullPointerException due to a ClassCastException
> -------------------------------------------------------------------------
>                 Key: CAMEL-11772
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-sjms
>    Affects Versions: 2.19.0, 2.19.1, 2.19.2
>            Reporter: Derek Wilhelm
>             Fix For: 2.19.4, 2.20.0
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> When using a camel-sjms endpoint with an Apache Artemis broker, the sjms endpoint will
throw a NullPointerException in the org.apache.camel.component.sjms.consumer.AbstractMessageHandler.onMessage
method.  However, this exception is actually masking the real exception within sjms.  In
the method getDestinationAsString gets called with a javax.jms.Destination object.  In this
case, it is a org.apache.activemq.artemis.jms.client.ActiveMQDestination.  The ActiveMQDestination
is neither a javax.jms.Topic nor a javax.jms.Queue.  In the getDestinationAsString method
in, it first checks to see if the destination is a Topic and then if it is
not it blindly casts to a javax.jms.Queue and in this case causes a ClassCastException.

This message was sent by Atlassian JIRA

View raw message