[
https://issues.apache.org/jira/browse/CAMEL-5722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13480941#comment-13480941
]
Willem Jiang commented on CAMEL-5722:
-------------------------------------
We have faced the same issue in camel-jaxb, to resolve it we put the bundle
class loader as application class laoder into the bus and it can be get by the
CXF run time, so the TCCL can be set with the application class loader whenever
the camel need.
@Raul, to resolve the issue that you faced, you can use the
CamelContext.getApplicationContxt() to set the TCCL on the
CamelContinuationServlet.
> 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
