You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Artur Jablonski <aj...@ravenpack.com> on 2017/11/15 15:06:25 UTC

Camel [2.19.3] + SpringBoot [1.5.6] fails executing two JUnit tests that succeed when run individually

Hello,

I've been looking at this issue with running integration tests in Camel +
SpringBoot combo context.

I have a route that fails to start in integration tests when CamelContext
starts up. That's expected. One of endpoints refers to a AWS resource that
the test running machine has no access to. That's OK too, I don't want to
poke the real resource in the test, so I use the adviceWith() to replace
the endpoint and start the camel context myself. This works well for a
single test. As soon as I add another test, the second test fails, because
of the complaints from the original endpoint about the permissions. It
looks as if before the second test runs the spring context starts up
together with the camel context (it seems to ignore the fact that the test
class is annotated with @UseAdviceWith).

This is a minimal testcase I could produce to reproduce the behaviour
https://gist.github.com/anonymous/626cf26197dd5a05569d4d306870a22e

What am I missing?

Best,
Artur

Re: Camel [2.19.3] + SpringBoot [1.5.6] fails executing two JUnit tests that succeed when run individually

Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Nov 16, 2017 at 3:49 PM, Artur Jablonski
<aj...@ravenpack.com> wrote:
> Hey,
>
> Nope, I tried with 2.19.4 and it was failing in the same way as 2.19.3. We
> felt brave yesterday and moved to 2.20.1. What's the worst thing that can
> happen? :)
>

Yay you get a set of known bugs fixed and some new unknown added ;)



>
>
> On Thu, Nov 16, 2017 at 3:42 PM, Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi
>>
>> If you want to stay on 2.19.x you may try 2.19.4 which could
>> potentially also have the fix.
>>
>> On Wed, Nov 15, 2017 at 4:39 PM, Artur Jablonski
>> <aj...@ravenpack.com> wrote:
>> > Sweet lord! This must be the fastest response ever... and yes indeed it
>> > works with 2.20.1.
>> >
>> > Thank you Claus
>> >
>> > Best,
>> > Artur
>> >
>> >
>> > On Wed, Nov 15, 2017 at 4:09 PM, Claus Ibsen <cl...@gmail.com>
>> wrote:
>> >
>> >> Hi
>> >>
>> >> I think we fixed something related to that, try with camel 2.20.1.
>> >> Or refactor your test classes to only have 1 test method when advicing
>> >>
>> >> On Wed, Nov 15, 2017 at 4:06 PM, Artur Jablonski
>> >> <aj...@ravenpack.com> wrote:
>> >> > Hello,
>> >> >
>> >> > I've been looking at this issue with running integration tests in
>> Camel +
>> >> > SpringBoot combo context.
>> >> >
>> >> > I have a route that fails to start in integration tests when
>> CamelContext
>> >> > starts up. That's expected. One of endpoints refers to a AWS resource
>> >> that
>> >> > the test running machine has no access to. That's OK too, I don't
>> want to
>> >> > poke the real resource in the test, so I use the adviceWith() to
>> replace
>> >> > the endpoint and start the camel context myself. This works well for a
>> >> > single test. As soon as I add another test, the second test fails,
>> >> because
>> >> > of the complaints from the original endpoint about the permissions. It
>> >> > looks as if before the second test runs the spring context starts up
>> >> > together with the camel context (it seems to ignore the fact that the
>> >> test
>> >> > class is annotated with @UseAdviceWith).
>> >> >
>> >> > This is a minimal testcase I could produce to reproduce the behaviour
>> >> > https://gist.github.com/anonymous/626cf26197dd5a05569d4d306870a22e
>> >> >
>> >> > What am I missing?
>> >> >
>> >> > Best,
>> >> > Artur
>> >>
>> >>
>> >>
>> >> --
>> >> Claus Ibsen
>> >> -----------------
>> >> http://davsclaus.com @davsclaus
>> >> Camel in Action 2: https://www.manning.com/ibsen2
>> >>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel [2.19.3] + SpringBoot [1.5.6] fails executing two JUnit tests that succeed when run individually

Posted by Artur Jablonski <aj...@ravenpack.com>.
Hey,

Nope, I tried with 2.19.4 and it was failing in the same way as 2.19.3. We
felt brave yesterday and moved to 2.20.1. What's the worst thing that can
happen? :)



On Thu, Nov 16, 2017 at 3:42 PM, Claus Ibsen <cl...@gmail.com> wrote:

> Hi
>
> If you want to stay on 2.19.x you may try 2.19.4 which could
> potentially also have the fix.
>
> On Wed, Nov 15, 2017 at 4:39 PM, Artur Jablonski
> <aj...@ravenpack.com> wrote:
> > Sweet lord! This must be the fastest response ever... and yes indeed it
> > works with 2.20.1.
> >
> > Thank you Claus
> >
> > Best,
> > Artur
> >
> >
> > On Wed, Nov 15, 2017 at 4:09 PM, Claus Ibsen <cl...@gmail.com>
> wrote:
> >
> >> Hi
> >>
> >> I think we fixed something related to that, try with camel 2.20.1.
> >> Or refactor your test classes to only have 1 test method when advicing
> >>
> >> On Wed, Nov 15, 2017 at 4:06 PM, Artur Jablonski
> >> <aj...@ravenpack.com> wrote:
> >> > Hello,
> >> >
> >> > I've been looking at this issue with running integration tests in
> Camel +
> >> > SpringBoot combo context.
> >> >
> >> > I have a route that fails to start in integration tests when
> CamelContext
> >> > starts up. That's expected. One of endpoints refers to a AWS resource
> >> that
> >> > the test running machine has no access to. That's OK too, I don't
> want to
> >> > poke the real resource in the test, so I use the adviceWith() to
> replace
> >> > the endpoint and start the camel context myself. This works well for a
> >> > single test. As soon as I add another test, the second test fails,
> >> because
> >> > of the complaints from the original endpoint about the permissions. It
> >> > looks as if before the second test runs the spring context starts up
> >> > together with the camel context (it seems to ignore the fact that the
> >> test
> >> > class is annotated with @UseAdviceWith).
> >> >
> >> > This is a minimal testcase I could produce to reproduce the behaviour
> >> > https://gist.github.com/anonymous/626cf26197dd5a05569d4d306870a22e
> >> >
> >> > What am I missing?
> >> >
> >> > Best,
> >> > Artur
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -----------------
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: Camel [2.19.3] + SpringBoot [1.5.6] fails executing two JUnit tests that succeed when run individually

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

If you want to stay on 2.19.x you may try 2.19.4 which could
potentially also have the fix.

On Wed, Nov 15, 2017 at 4:39 PM, Artur Jablonski
<aj...@ravenpack.com> wrote:
> Sweet lord! This must be the fastest response ever... and yes indeed it
> works with 2.20.1.
>
> Thank you Claus
>
> Best,
> Artur
>
>
> On Wed, Nov 15, 2017 at 4:09 PM, Claus Ibsen <cl...@gmail.com> wrote:
>
>> Hi
>>
>> I think we fixed something related to that, try with camel 2.20.1.
>> Or refactor your test classes to only have 1 test method when advicing
>>
>> On Wed, Nov 15, 2017 at 4:06 PM, Artur Jablonski
>> <aj...@ravenpack.com> wrote:
>> > Hello,
>> >
>> > I've been looking at this issue with running integration tests in Camel +
>> > SpringBoot combo context.
>> >
>> > I have a route that fails to start in integration tests when CamelContext
>> > starts up. That's expected. One of endpoints refers to a AWS resource
>> that
>> > the test running machine has no access to. That's OK too, I don't want to
>> > poke the real resource in the test, so I use the adviceWith() to replace
>> > the endpoint and start the camel context myself. This works well for a
>> > single test. As soon as I add another test, the second test fails,
>> because
>> > of the complaints from the original endpoint about the permissions. It
>> > looks as if before the second test runs the spring context starts up
>> > together with the camel context (it seems to ignore the fact that the
>> test
>> > class is annotated with @UseAdviceWith).
>> >
>> > This is a minimal testcase I could produce to reproduce the behaviour
>> > https://gist.github.com/anonymous/626cf26197dd5a05569d4d306870a22e
>> >
>> > What am I missing?
>> >
>> > Best,
>> > Artur
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: Camel [2.19.3] + SpringBoot [1.5.6] fails executing two JUnit tests that succeed when run individually

Posted by Artur Jablonski <aj...@ravenpack.com>.
Sweet lord! This must be the fastest response ever... and yes indeed it
works with 2.20.1.

Thank you Claus

Best,
Artur


On Wed, Nov 15, 2017 at 4:09 PM, Claus Ibsen <cl...@gmail.com> wrote:

> Hi
>
> I think we fixed something related to that, try with camel 2.20.1.
> Or refactor your test classes to only have 1 test method when advicing
>
> On Wed, Nov 15, 2017 at 4:06 PM, Artur Jablonski
> <aj...@ravenpack.com> wrote:
> > Hello,
> >
> > I've been looking at this issue with running integration tests in Camel +
> > SpringBoot combo context.
> >
> > I have a route that fails to start in integration tests when CamelContext
> > starts up. That's expected. One of endpoints refers to a AWS resource
> that
> > the test running machine has no access to. That's OK too, I don't want to
> > poke the real resource in the test, so I use the adviceWith() to replace
> > the endpoint and start the camel context myself. This works well for a
> > single test. As soon as I add another test, the second test fails,
> because
> > of the complaints from the original endpoint about the permissions. It
> > looks as if before the second test runs the spring context starts up
> > together with the camel context (it seems to ignore the fact that the
> test
> > class is annotated with @UseAdviceWith).
> >
> > This is a minimal testcase I could produce to reproduce the behaviour
> > https://gist.github.com/anonymous/626cf26197dd5a05569d4d306870a22e
> >
> > What am I missing?
> >
> > Best,
> > Artur
>
>
>
> --
> Claus Ibsen
> -----------------
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: Camel [2.19.3] + SpringBoot [1.5.6] fails executing two JUnit tests that succeed when run individually

Posted by Claus Ibsen <cl...@gmail.com>.
Hi

I think we fixed something related to that, try with camel 2.20.1.
Or refactor your test classes to only have 1 test method when advicing

On Wed, Nov 15, 2017 at 4:06 PM, Artur Jablonski
<aj...@ravenpack.com> wrote:
> Hello,
>
> I've been looking at this issue with running integration tests in Camel +
> SpringBoot combo context.
>
> I have a route that fails to start in integration tests when CamelContext
> starts up. That's expected. One of endpoints refers to a AWS resource that
> the test running machine has no access to. That's OK too, I don't want to
> poke the real resource in the test, so I use the adviceWith() to replace
> the endpoint and start the camel context myself. This works well for a
> single test. As soon as I add another test, the second test fails, because
> of the complaints from the original endpoint about the permissions. It
> looks as if before the second test runs the spring context starts up
> together with the camel context (it seems to ignore the fact that the test
> class is annotated with @UseAdviceWith).
>
> This is a minimal testcase I could produce to reproduce the behaviour
> https://gist.github.com/anonymous/626cf26197dd5a05569d4d306870a22e
>
> What am I missing?
>
> Best,
> Artur



-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2