Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-10406

VM endpoint caching leak the wrong camel context

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.17.4, 2.18.1, 2.19.0
    • Component/s: camel-core
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                davsclaus Claus Ibsen
                Reporter:
                xfournet Xavier Fournet
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: