JmsCourier should be allowed to overwrite outgoing JMS Message properties. -------------------------------------------------------------------------- Key: JBESB-2771 URL: https://jira.jboss.org/jira/browse/JBESB-2771 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta, Transports Affects Versions: 4.6 Reporter: Daniel Bevenius Assignee: Daniel Bevenius Fix For: 4.7 When a JmsCourier is created and is specified to be a sender (isReciever=false), the passed in JMSEPR's message selector is stored in a field (_messageProperties which is a List of KeyValuePairs). When this JmsCourier is going to deliver a JMS Message it will iterate through the properties and set them on the outgoing JMS Message. The problem here is that the current implementation will first check to see if the JMS Message already has a property with the same key set on it, and if it has, will not overwrite the value. This is a problem because before this is done the JMSPropertiesStrategy will have been run and might for example have set the 'jbossESBresponseUUID' causing and old and invalid message selector to be passed through. This can be fixed by letting the JmsCourier have the last say and overwrite message properties. Or an explicit check could be add for 'jbossESBresponseUUID'. This issue was reported by Toshiya Kobayashi who also provided some nice examples that reproduce this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira