Hello.
I recently changes some routes to use SEDA instead of direct and since then
started to get ClassCastException on the following code in my processor.
JmsMessage in = (JmsMessage) exchange.getIn();
ActiveMQTextMessage activeMQTextMessage = (ActiveMQTextMessage)
in.getJmsMessage();
String connectionId = activeMQTextMessage.getProducerId().getConnectionId();
exchange.getIn().setHeader("connectionId", connectionId);
LOG:
Error Extracting message java.lang.ClassCastException:
org.apache.camel.impl.DefaultMessage cannot be cast to
org.apache.camel.component.jms.JmsMessage
I understand that SEDA causes things to be async but what can be the reason
for the type change ?
PS If there is a better way to get the JMS connection ID that would be
great.
I'm using Camel 2.0 with AMQ 5.2
Thanks.
--
View this message in context:
http://www.nabble.com/Cahnging-endpoint-from-SEDA-to-direct-causes-ClassCastException-tp25487639p25487639.html
Sent from the Camel - Users mailing list archive at Nabble.com.
