Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 27 Oct 2012 17:07:12 +0000 (UTC)
From: "Raul Kripalani (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <2054382730.35379.1351357632829.JavaMail.jiratomcat@arcas>
In-Reply-To: <1363449652.5638.1350749052329.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CAMEL-5722) Classloader mixup when consumers
 across bundles share the same camel-jetty port
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485473#comment-13485473 ] 

Raul Kripalani commented on CAMEL-5722:
---------------------------------------

I think this can also be a problem in the Direct VM component, if a new Exchange is not created at the consumer side... I'll check.
                
> Classloader mixup when consumers across bundles share the same camel-jetty port
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-5722
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5722
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jetty
>    Affects Versions: 2.8.0
>         Environment: OSGi environment, Karaf 2.2.2.
>            Reporter: Raul Kripalani
>            Assignee: Raul Kripalani
>            Priority: Critical
>
> Happens in an OSGi environment; but it is also applicable in modular servers that build dynamic classloaders (e.g. JBoss AS) per deployed artifacts (WAR, module, EAR, etc.).
> If bundles A and B are both creating camel-jetty consumers on the same TCP port, the consumers will share the underlying Jetty connector. Moreover, the Jetty connector is indeed created by the first consumer that initialises on that TCP port.
> Since the Camel route executes on the Jetty Connector thread, all class resolutions will happen against the classloader of the bundle that initialises first.
> This makes class resolution absolutely undeterministic and erratic. Quite a nasty bug IMHO.
> Perhaps this can be fixed by adding a call to {{Thread.setContextClassLoader()}} passing the classloader of the JettyHttpEndpoint, as soon as a request comes in?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira