Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <2001954486.1258390552788.JavaMail.jira@brutus>
Date: Mon, 16 Nov 2009 08:55:52 -0800 (PST)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-2177) Initialization of
 DefaultTypeConverter should only let one do the classpath scanning for
 @Converter
In-Reply-To: <1784686047.1258378912791.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen resolved CAMEL-2177.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.2.0)
                   2.1.0
         Assignee: Claus Ibsen

trunk: 880843.

Loading improved but it was likely newer multiple threads loading anyway. But the code is improved.

Fixed the WARN logging when race conditions occur with multiple threads promoting a fallback converter.

> Initialization of DefaultTypeConverter should only let one do the classpath scanning for @Converter
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2177
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2177
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.0.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.1.0
>
>
> In cases multiple requests hit Camel really fast after startup, a race condition can lead to multiple threads doing concurrent classpath scanning for @Converter

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.