3 Replies Latest reply on Apr 10, 2013 3:46 AM by jasonnh

CamelBlueprintTestSupport intermittent camelContext loading problem

jasonnh Mar 12, 2013 1:05 PM

Hi,

I have some camel routes defined in blueprint doing a variety of things covered by unit tests using CamelBlueprintTestSupport.

Normally the tests pass but approximately every 15-20 attempts they fail with the error:

2013-03-12 15:45:27,317 INFO  CamelBlueprintHelper - Deleting work directory target/bundles/1363103126713 
2013-03-12 15:45:27,319 DEBUG TestSupport - tearDownAfterClass test 
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 36.082 sec <<< FAILURE!
testMyTest(com.company.MyRouteTest)  Time elapsed: 30.185 sec  <<< ERROR!
java.lang.RuntimeException: Gave up waiting for service (objectClass=org.apache.camel.CamelContext)
     at org.apache.camel.test.blueprint.CamelBlueprintHelper.getOsgiService(CamelBlueprintHelper.java:203)
     at org.apache.camel.test.blueprint.CamelBlueprintHelper.getOsgiService(CamelBlueprintHelper.java:161)
     at org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createCamelContext(CamelBlueprintTestSupport.java:116)
     at org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:247)
     at org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:217)
     at org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:50)

The only pattern I can find is that it looks like the class is trying to delete the temp bundles folder and then times out due to the 30 second timeout. Increasing the timeout does not help. However, as there is no DEBUG log confirming that directory has been deleted then this may be misleading.

Does anybody know of problems with CamelBlueprintTestSupport?

For example, could something have a lock on one of the files in the bundles temp folder which stops it being deleted?

Thanks.

Edited by: jasonnh on Mar 12, 2013 5:03 PM

1. Re: CamelBlueprintTestSupport intermittent camelContext loading problem

davsclaus Mar 13, 2013 5:39 AM (in response to jasonnh)

Hi

Yeah I have seen this from time to time as well. You can run the tests 100 times, and it may fail a few times etc. Not sure what happens, if its pojosr or blueprint etc. Though OSGi and Blueprint has a really complicated startup model where all is async, and kinda waiting for each other. And that is dead hard to test throughly.

You can try setting the surefire plugin to fork the jvm per test. Then its a full fresh JVM on each test. This may fix this, in case there is some "left over" when running all the test in the same JVM.
Actions
2. Re: CamelBlueprintTestSupport intermittent camelContext loading problem

jasonnh Mar 13, 2013 12:39 PM (in response to davsclaus)
Thanks.

Unfortunately, I tried forking and that did not seem to help.

I noticed the comment below which is just above the 'Gave up waiting.." log statement in CamelBlueprintHelper.java.

// Note that the tracker is not closed to keep the reference // This is buggy, as the service reference may change i think

Which sounds bad although I guess it is talking more about getting the service reference and then it changing later while it is being used rather than not getting it in the first place.
Actions
3. Re: CamelBlueprintTestSupport intermittent camelContext loading problem

jasonnh Apr 10, 2013 3:46 AM (in response to jasonnh)

Could this problem be related to the following?:

https://issues.apache.org/jira/browse/CAMEL-6068
Actions

Go to original post