[
https://issues.apache.org/jira/browse/CAMEL-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435783#comment-15435783
]
ASF GitHub Bot commented on CAMEL-10269:
----------------------------------------
GitHub user ssharma opened a pull request:
https://github.com/apache/camel/pull/1139
Optimize DefaultCamelContext#getComponent CAMEL-10269
#CAMEL-10269
Add DCL idiom to lower lock semantics and used CHM. Didn't retrofit put to
use putIfAbsent as the change would have been instrusive
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ssharma/camel CAMEL-10269
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1139.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1139
----
commit 0a72d3fefb62368d701b51e02abe179ac0efa25d
Author: Siddharth Sharma <[email protected]>
Date: 2016-08-24T21:53:25Z
Optimize DefaultCamelContext#getComponent CAMEL-10269
----
> Optimize DefaultCamelContext#getComponent
> -----------------------------------------
>
> Key: CAMEL-10269
> URL: https://issues.apache.org/jira/browse/CAMEL-10269
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.18.0
> Reporter: Siddharth Sharma
> Priority: Minor
> Fix For: 2.18.0
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
