[CAMEL-10406] VM endpoint caching leak the wrong camel context

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 2.17.4, 2.18.1, 2.19.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Xavier Fournet
• Created: 20/Oct/16 22:06
• Updated: 25/Jan/17 16:18
• Resolved: 29/Oct/16 19:55

Description

When consuming from a vm: endpoint, the camel context of the consumed exchange may be the wrong one.
The method org.apache.camel.component.seda.SedaConsumer#prepareExchange is expected to set the adequate camel context, but because of the Endpoint caching in org.apache.camel.component.vm.VmComponent#ENDPOINTS the first context that create the endpoint win. In case the first context is the producer one, the route in the consumer may fail when trying to access to some information from the context

Repro case available here: https://github.com/xfournet/camel/blob/CAMEL-10406/camel-core/src/test/java/org/apache/camel/component/vm/VmShouldUseConsumerContext.java

This is related to CAMEL-6746, reverting this code make this test pass but obviously some other vm test failed.

Issue Links

• is related to: CAMEL-10747 CamelContext is not been set in VMConsumer when used with POJO @Consume