NPE when multiple bundles have context-weaving enabled

amy

pleteRefresh(AbstractDelegatedExecutionApplicationContext.java:288) at org..osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExec at com..server.kernel.dm.ContextPropagatingTaskExecutor$2.run(ContextPropagatingTaskExecutor.java:82) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) I don't think I'm doing anything wrong because when I switch the order of deploying the bundles, the one that was loaded second and didn't work then initializes OK, while the other bundle that was OK before, fails to initialize properly when loaded second. The bundles are nothing special, they use EclipseLink and annotation-based transactions, as per the PetClinic example. Is this something that is expected (and if so is there a workaround?), or should I report this as a bug?
TIA!

Hmm, that doesn't look good. Is it possible for you to create a bug report for this? And if possible, can you attach your bundles? If you don't want to attach them to the public issue you can send them directly to me - I'd really like to see what is amiss here.

Regards,

Rob


Originally Posted by robhHmm, that doesn't look good. Is it possible for you to create a bug report for this? And if possible, can you attach your bundles? If you don't want to attach them to the public issue you can send them directly to me - I'd really like to see what is amiss here.

No problem, thanks for the quick reply. I've reported it through the tracker: here and attached two really basic bundles that reproduce the problem. Let me know if you need any more info.

Thanks for that, we'll take a look at this ASAP.