The TestRegistrationListener test is failing because the “serviceRegistered”
method is never called. However, the serviceUnregistere method is called
twice. The first call has a stack trace of:
at
org.apache.aries.blueprint.utils.ReflectionUtils.invoke(ReflectionUtils.java:297)
at
org.apache.aries.blueprint.utils.ServiceListener.invokeMethod(ServiceListener.java:97)
at
org.apache.aries.blueprint.utils.ServiceListener.unregister(ServiceListener.java:64)
at
org.apache.aries.blueprint.container.ServiceRecipe.createService(ServiceRecipe.java:321)
at
org.apache.aries.blueprint.container.ServiceRecipe.internalGetService(ServiceRecipe.java:250)
at
org.apache.aries.blueprint.container.ServiceRecipe.internalGetService(ServiceRecipe.java:237)
at
org.apache.aries.blueprint.container.ServiceRecipe.getClasses(ServiceRecipe.java:376)
at
org.apache.aries.blueprint.container.ServiceRecipe.register(ServiceRecipe.java:184)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.registerServices(BlueprintContainerImpl.java:703)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:377)
at
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:269)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
which I find completely bizarre. It’s within ServiceRecipe.register, but
unregister is being called?
Dan
On Dec 13, 2013, at 3:36 PM, Daniel Kulp <dk...@apache.org> wrote:
>
> While writing a test for ARIES-1141, I discovered that the blueprint-itests
> were pulling in “org.apache.aries.blueprint/1.0.0” which is the older “big
> blueprint bundle” instead of the individual “core”, “cm”, etc… bundles.
> There are several issues:
>
> 1) Since karaf and everything has been updated to using the littler bundles,
> this means we aren’t testing what people are using
>
> 2) We haven’t done a “release” of the big bundle since 1.0.0, but there have
> been releases of the littler things. This means the littler things haven’t
> had the itests run with them.
>
> 3) I flipped the itests to use the little bundles and now we have couple of
> test failures.
>
> Running org.apache.aries.blueprint.itests.TestRegistrationListener
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.968 sec <<<
> FAILURE!
> Running org.apache.aries.blueprint.itests.BlueprintContainerTest
> Tests run: 4, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 48.701 sec
> <<< FAILURE!
>
>
> org.apache.aries.blueprint.itests.ASMMultiBundleTest also fails
> semi-randomly. That may be the sync vs non-sync startup issues. Need to
> double check that.
>
>
> If you have some time, please try taking a look. It looks like we may have
> broken a bunch of things through the various releases and that obviously
> concerns me. The BlueprintContainerTest is in testScheduledExecMemoryLeak
> which kind of scares me.
>
>
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
