After going through with a fine tooth comb, I think the issue might be the instance of connection factory. The only difference between your test case and what I am doing is that I am getting the connection factory by doing a jndi lookup on a resource adapter that is configured in my jboss j2ee container. the connection factory that it gives back is an instance of
*org.apache.activemq.ra.ActiveMQConnectionFactory* which i am feeding to the jmscomponent and running into this issue, if I don't use it and instantiate a new connection factory of type * org.apache.activemq.ActiveMQConnectionFactory * there might be some additional properties that I have to set on the resource adapter for this to work, I am not sure. -- View this message in context: http://camel.465427.n5.nabble.com/JMS-message-with-Inout-pattern-tp5787336p5787431.html Sent from the Camel - Users mailing list archive at Nabble.com.
