[CAMEL-10269] Optimize DefaultCamelContext#getComponent

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.18.0
• Component/s: camel-core
• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Siddharth Sharma
• Created: 24/Aug/16 21:34
• Updated: 05/Sep/16 07:18
• Resolved: 05/Sep/16 07:18

Description

While debugging how components are resolved by Camel, noticed DefaultCamelContext#getComponent locks on components HashMap for the entire duration the component is created and started. This leads to other threads blocking on getComponent as if the entire method is synchronized

Issue Links

• links to: GitHub Pull Request #1139
• links to: GitHub Pull Request #1152