[CAMEL-18210] camel-core - Pooled exchanges in batch consumer may use an exchange concurrently

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.14.3, 3.17.0
• Fix Version/s: 3.14.4, 3.18.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 20/Jun/22 14:00
• Updated: 20/Jun/22 16:35
• Resolved: 20/Jun/22 16:34

Description

A pooled exchange may mistakenly be added twice back into the pool, and then reused concurrently if a batch consumer have 2+ exchanges in a batch to process.

Issue Links

• breaks: CAMEL-18185 slack: npe when processing batch messages
• breaks: CAMEL-18187 slack: inconsistent message payload when batch ends