You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2016/09/05 07:19:21 UTC

[jira] [Resolved] (CAMEL-10269) Optimize DefaultCamelContext#getComponent

     [ https://issues.apache.org/jira/browse/CAMEL-10269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-10269.
---------------------------------
    Resolution: Fixed

Thanks for the PR

> Optimize DefaultCamelContext#getComponent
> -----------------------------------------
>
>                 Key: CAMEL-10269
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10269
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            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)