Closed GoogleCodeExporter closed 9 years ago
The issue has been verified in a test lab and debugger. The root cause is due
to an improper assertion of how the Camel aggregation pattern works when
messages are timed out. The aggreator removed the messages from the
aggregation store before the DSN error message is sent. When the DSN message
is received by the message monitor, all context to the original message has
been deleted, and the message is not properly added to the duplication store.
The solution will detect timeout conditions and add the message to the
duplication store immediately upon timeout instead of waiting for the DSN
failure message to be tracked (assuming that the message has requested the
timely and reliable protocol).
Original comment by gm2...@cerner.com
on 10 Dec 2012 at 4:25
Issue resolved and tested internal test lab. Need to retest with previous test
partner and validate.
Original comment by gm2...@cerner.com
on 13 Dec 2012 at 2:31
Closing after testing with partner.
Original comment by gm2...@cerner.com
on 25 Jun 2013 at 2:23
Original issue reported on code.google.com by
gm2...@cerner.com
on 10 Dec 2012 at 4:22