[SM-1861] JMSFlow handles sendSync timeouts incorrectly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 3.3
• Component/s: servicemix-core
• Assignee: Unassigned
• Reporter: Maciej Prochniak
• Created: 04/Jun/09 13:33
• Updated: 26/Mar/13 13:36
• Resolved: 26/Mar/13 13:36

Description

When timeout happens during sendSync the message exchange is aborted. This is done on sender's side. When using JMSFlow the MessageExchange object is (de)serialized, so provider gets copy of it and is not aware of message being aborted. It seems not to conform to 5.5.2.1.3 of JBI specification, moreover the behaviour depends significantly on flow being used.