[CAMEL-4401] StreamResequencer poisoned by bad Exchange

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.7.1
• Fix Version/s: 2.9.0
• Component/s: camel-core

Environment

JDK 1.6.0_20, Linux x86_64

• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: David Tombs
• Created: 31/Aug/11 17:15
• Updated: 14/Sep/11 09:31
• Resolved: 13/Sep/11 15:43

Description

If a StreamResequencer's configured Expression returns null for an Exchange (e.g., if a header does not exist) and the resequencer's pipeline is currently empty, the bad Exchange will be added to the pipeline. ResequencerEnginer.insert() succeeds in calling sequence.add() with the bad Exchange, but throws an Exception when calling sequence.successor(). This results in the message ending up at the Error Handler but the bad Exchange still in the Engine's sequence. Probably insert() should be probably be more transactional.

After this happens:
1) Trying to add a further exchange (even a "good" one) results in an Exception when calling sequence.add().
2) ResequencerEngine.deliverNext() results in an Exception so no further messages will be delievered.

I will attach a unit test to reproduce when I get a chance.