[CAMEL-6377] Optimize routing engine to reduce stack frames in use during routing and reduce callbacks

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.12.0
• Fix Version/s: 2.12.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Claus Ibsen
• Created: 18/May/13 14:23
• Updated: 09/Sep/14 13:08
• Resolved: 30/Jul/13 08:10

Description

We can optimize the Camel routing engine internally, and redue the need for wrapping processors (those internally used for cross cutting functionality) where they would wrap each other one by one; which then results in larger call stacks during routing.

This also shows to end users when stacktraces is being logged etc, as they tend to be a bit longer with many internal calls.

Though the JVM optimizes this at runtime as it can inline the calls and whatnot. But the stacktraces is still shown expanded.

Issue Links

• breaks: CAMEL-7795 Regression: MDC may lose values after when Async Routing Engine is used
• relates to: CAMEL-6581 SendProcessor - Use fixed destination allow routing engine optimizations