anonymous wrote : Have you got an example which shows this going wrong? The example here is an action that uses the ServiceInvoker to call another service in the ESB. This called service uses a MEP (Message Exchange Pattern) of 'RequestResponse'. Having multiple of these actions in the pipeline would cause the 'jbossESBresponseUUID' to stay unchanged, which will cause message pickup to fail as there is no match for the new selector. anonymous wrote : If this is specific to the transport then we should aim to have the transport clean it up before the message is delivered and not have it leak through. Can you see an easy way to do this? We could set specify a filter pattern for the DefaultESBPropertiesSetter: | /** | * Filter pattern for incoming property keys. These are properties that should not be | * extracted from the JMS Message object into the ESB Message object. | */ | private static final String INPUT_PROPERTIES_FILTER = DefaultJmsReplyToEpr.REPLY_UUID_TAG; | | /** | * Strategy for setting JMS Properties on the ESB Message object created | * by the process method. | */ | private ESBPropertiesSetter esbPropertiesStrategy = new DefaultESBPropertiesSetter(INPUT_PROPERTIES_FILTER); | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248139#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...