I faces with situation when properties of NormalizedMessage can be lost in the way between endpoints. It does not depend on type of endpoint. The problem is not stable, but possible to catch. For example if we lost special property for eip: resequencer/eip:asyncbridge and it will not work properly. Also I tried to change SedaFlow to JMSFlow, but it seems JMSFlow does not copy properties at all. I'm right? if so use of eip:asyncBridge and eip:resequencer can be difficult.
I've just created JIRA (https://issues.apache.org/activemq/browse/SM-1932) and provided reproducer. -- View this message in context: http://old.nabble.com/Problem-with-NormalizedMessage-properties-tp27531840p27531840.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
