[ http://jira.jboss.com/jira/browse/JBESB-1622?page=comments#action_12405012 ] Daniel Bevenius commented on JBESB-1622: ---------------------------------------- Hi Tom, just wanted to let you know about this jira : http://jira.jboss.com/jira/browse/JBESB-1559 just in case you havn't seen it previously. It also concered the message ID getting overritten by the JMSMessageID /Daniel -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1622?page=all ] Tom Cunningham updated JBESB-1622: ---------------------------------- Summary: Need to add an ESB reply to header (was: Need to make sure that Message ID is not overwritten by JMS message ID) Fix Version/s: 4.3 Affects Version/s: 4.2.1 (was: 4.2.1 CP1) Description: Need to make sure that the message ID is not overwritten by the JMS message ID. The message ID is going to be used to correlate reply-to messages and link message metadata - we're going to need them to be consistent so for monitoring. EDIT : the fix from the bug Daniel talks about below needs to be merged back into CP branch. was:Need to make sure that the message ID is not overwritten by the JMS message ID. The message ID is going to be used to correlate reply-to messages and link message metadata - we're going to need them to be consistent so for monitoring. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1622?page=all ] Mark Little reassigned JBESB-1622: ---------------------------------- Assignee: Daniel Bevenius -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1622?page=comments#action_12414221 ] Daniel Bevenius commented on JBESB-1622: ---------------------------------------- So, I'll update the CP branch with the messsageID fix, no problem there... But I'm not sure what I should do for the reply-to. Does this mean that we should set it on the body in a named location? Or does this mean that the Call class should be extended with an additional reply-to? Perhaps I'm interpreting the "header" mentioned in the above comment incorrectly. Thanks, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1622?page=comments#action_12420787 ] Kevin Conner commented on JBESB-1622: ------------------------------------- Discussed at f2f: We need to determine a test to see whether the setting of the reply to within DefaultESBPropertiesSetter will be problematic. This information should only be set on the incoming gateways and should not be modified with messages travelling within the ESB. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-1622?page=all ] Work on JBESB-1622 started by Daniel Bevenius. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira