You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Zoran Regvart (JIRA)" <ji...@apache.org> on 2017/09/26 08:41:01 UTC

[jira] [Resolved] (CAMEL-11814) camel-spring-boot - Recent change in startup behaviour can cause camel-test-spring problems

     [ https://issues.apache.org/jira/browse/CAMEL-11814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zoran Regvart resolved CAMEL-11814.
-----------------------------------
    Resolution: Fixed

I've changed the {{NO_START}} flag to be a global (static) {{AtomicBoolean}} this will help with race conditions between {{CamelMainRunController}} and {{SpringCamelContext/CamelContextFactoryBean}} on different threads.

This fix conditions itself upon different {{(Spring}CamelContexts}} being in different classloaders to work.

> camel-spring-boot - Recent change in startup behaviour can cause camel-test-spring problems
> -------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-11814
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11814
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-spring, camel-spring-boot
>    Affects Versions: 2.20.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.20.0
>
>
> Creating this ticket up front as I was testing CiA2 source code with 2.20.0-SNAPSHOT and have issues with a camel spring boot app, that caused the test method to be executed without CamelContext been started prior - this works fine on 2.19.x and older versions.
> Its very likely the new startup/shutdown change in camel-spring / camel-spring-boot that is causing a regression problem. A bit weird our own set of unit tests at Apache Camel hasn't triggered this.
> Doing some more testing on CiA2 before posting more information here.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)