CamelBlueprintTestSupport version

[Ranx <br...@mediadriver.com>]

I believe Quinn mentioned that a new snapshot version of CBTS is out that
fixes a race problem.  I'm getting errors in 2.15 that definitely have the
smell of a threading problem.  Most of the time my tests run fine but then,
every once in awhile, it will just hang when I go to call getOSGiService. 
If I re-run the build immediately it will usually pass.  

This isn't a timeout issue as I can jack that up to whatever number I want
and the tests will either pass with flying colors or it'll just hit one that
hangs every now and again.  I can't reliably replicate the behavior and
that's why I think it has the smell of a thread race/deadlock.



--
View this message in context: http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-version-tp5777764.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CamelBlueprintTestSupport version

[Ranx <br...@mediadriver.com>]

Overall I like the design of CBTS.  I like the veracity of Pax Exam but don't
care for all the moving parts.  I'm sure it would be quite a headache to
fork CBTS and replace PojoSR with Karaf but to me that would be the best of
both worlds.

By definition any Camel testing is really integration testing, they are
rarely unit tests in any meaningful sense.  With all the configuration
issues, classloader issues, etc. it makes it tough to test and deploy the
same code.  I end up debugging CBTS tests a lot and then find out that
something doesn't work right in deployment anyway.

Personally I'm willing to live with slower running tests if I get more
veracity from them. 



--
View this message in context: http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-version-tp5777764p5777796.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CamelBlueprintTestSupport version

[Ranx <br...@mediadriver.com>]

Wow! That's spectacular work.  Well done sir.

On Mon, Feb 15, 2016 at 11:20 PM, Grzegorz Grzybek [via Camel] <
ml-node+s465427n5777773h88@n5.nabble.com> wrote:

> Hello
>
> See http://ggrzybek.blogspot.com/2015/12/camel-blueprint-test-support.html
> for the details on:
>  - what was the original problem
>  - how it was fixed in newer versions (and in which versions)
>  - how the solution evolved over time and what were the timing issues
> you've hit
>
> You're right, it *was* thread race/deadlock problem.
>
> regards
> Grzegorz Grzybek
>
> 2016-02-16 4:54 GMT+01:00 Ranx <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5777773&i=0>>:
>
> > For whatever it's worth for whomever might run into a similar problem, I
> > think I've identified at least one trigger.
> >
> > My blueprint-properties.xml is defined with:
> > <cm:property-placeholder persistent-id="my.pid"
> update-strategy="reload">
> >
> > By creating a test-blueprint-properties.xml with the same information in
> it
> > but no reload strategy the intermittent hang seems to have stopped.
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-version-tp5777764p5777772.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-version-tp5777764p5777773.html
> To unsubscribe from CamelBlueprintTestSupport version, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5777764&code=YnJhZC5qb2huc29uQG1lZGlhZHJpdmVyLmNvbXw1Nzc3NzY0fDI4MjkxODI4OQ==>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-version-tp5777764p5777795.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CamelBlueprintTestSupport version

[Grzegorz Grzybek <gr...@gmail.com>]

Hello

See http://ggrzybek.blogspot.com/2015/12/camel-blueprint-test-support.html
for the details on:
 - what was the original problem
 - how it was fixed in newer versions (and in which versions)
 - how the solution evolved over time and what were the timing issues you've hit

You're right, it *was* thread race/deadlock problem.

regards
Grzegorz Grzybek

2016-02-16 4:54 GMT+01:00 Ranx <br...@mediadriver.com>:
> For whatever it's worth for whomever might run into a similar problem, I
> think I've identified at least one trigger.
>
> My blueprint-properties.xml is defined with:
> <cm:property-placeholder persistent-id="my.pid" update-strategy="reload">
>
> By creating a test-blueprint-properties.xml with the same information in it
> but no reload strategy the intermittent hang seems to have stopped.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-version-tp5777764p5777772.html
> Sent from the Camel - Users mailing list archive at Nabble.com.

Re: CamelBlueprintTestSupport version

[Ranx <br...@mediadriver.com>]

For whatever it's worth for whomever might run into a similar problem, I
think I've identified at least one trigger.  

My blueprint-properties.xml is defined with:
<cm:property-placeholder persistent-id="my.pid" update-strategy="reload">

By creating a test-blueprint-properties.xml with the same information in it
but no reload strategy the intermittent hang seems to have stopped.  



--
View this message in context: http://camel.465427.n5.nabble.com/CamelBlueprintTestSupport-version-tp5777764p5777772.html
Sent from the Camel - Users mailing list archive at Nabble.com.