[CAMEL-5722] Classloader mixup when consumers across bundles share the same camel-jetty port

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.9.5, 2.10.3, 2.11.0
• Component/s: camel-jetty

Environment

OSGi environment, Karaf 2.2.2.

• Estimated Complexity: Unknown
• Assignee: Raúl Kripalani
• Reporter: Raúl Kripalani
• Created: 20/Oct/12 16:02
• Updated: 27/Oct/12 18:33
• Resolved: 27/Oct/12 18:33

Description

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?

Issue Links

• is related to: CAMEL-5748 Classloader mixup in Direct VM component