Upon further investigation it seems to not be that simple. The basis of the route is as follows:
Send request to JMS Queue A -> Splitter on Response -> For each split, JMS Queue B So it seems that after A is evaluated, if you reset the JMS headers servicemix will start throwing null pointer exceptions. I don't have enough understanding of the activeMQ endpoint lifecycle to really troubleshoot this much more, so any insight or ideas would be helpful. I have tested and if I remove Queue A and instead mimic it's behavior witha static message that gets split, there are no collisions and the JMS Ids do not remain static as they do when Queue A is in scope. -- View this message in context: http://camel.465427.n5.nabble.com/JMS-Header-Issue-tp5129929p5129999.html Sent from the Camel - Users mailing list archive at Nabble.com.
