[CAMEL-16737] camel-core - Transacted vs reactive routing engine

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 4.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Claus Ibsen
• Created: 20/Jun/21 06:25
• Updated: 03/Sep/22 07:58

Description

Lets look at if we can make transacted work better with the reactive routing engine.

See CAMEL-16734 and the ticket it mentions for background.

Maybe we could let the routing engine be aware if a task is under transaction and execute it synchronously via its current thread, and ensure any other tasks that this thread or exchange is providing to the reactive engine is processed under the transaction via that same thread.

At this movement its the EIP implementation that need to splitup their tasks into transacted vs non-transacted which would ideally be avoided.

Issue Links

• is related to: CAMEL-16734 Recipient list does not wait for processing an exchange by recipients and ignores aggregation strategy when route is transacted.
• is related to: CAMEL-17401 Transacted Flag not copied by AbstractExchange.copy method