camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rsteppac2 <r...@steppacher.name>
Subject Sending/Receiving active-mq with transferExchange silently removes Exchange headers
Date Wed, 22 Feb 2017 13:30:07 GMT
Hello all,

I tried to migrate a route from using the "direct" endpoint to using the
ActiveMQ endpoint. I ran into an issue with exchange headers that contain
arrays of Strings. They get rejected with a MessageFormatException:

Failed delivery for (MessageId:
ID-Ralfs-MacBook-Pro-local-56776-1487752967901-2-233 on ExchangeId:
ID-Ralfs-MacBook-Pro-local-56776-1487752967901-2-234). Exhausted after
delivery attempt: 1 caught: org.springframework.jms.MessageFormatException:
Only objectified primitive objects, String, Map and List types are allowed
but was: [Ljava.lang.String;@51b56ff5 type: class [Ljava.lang.String;;
nested exception is javax.jms.MessageFormatException: Only objectified
primitive objects, String, Map and List types are allowed but was:
[Ljava.lang.String;@51b56ff5 type: class [Ljava.lang.String;

The way I read the documentation of the "transferExchange" property on the
camel-jms page I thought it would take care of this issue. The documentation
claims all serializable headers would be transferred. However, while the
exception is not thrown anymore, the string array headers get stripped from
the Exchange during the amq transport step. Is this the expected behavior or
should I raise an issue?


Thanks!
Ralf



--
View this message in context: http://camel.465427.n5.nabble.com/Sending-Receiving-active-mq-with-transferExchange-silently-removes-Exchange-headers-tp5794278.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Mime
View raw message