Anyone else get SPDE when accessing injected BambooUserManager in a Bamboo Plugin Task Configurator?

Dana Cleveland

This plugin worked fine on Bamboo 5.4.x. I have recently upgraded to 5.5. After a people fills out a form on this task, The TaskConfigurator attempts to access the BambooUserManager to retrieve user information to save for the actual Task.

No I'm getting

2014-06-26 22:51:42,111 ERROR [ajp-bio-8009-exec-56] [FiveOhOh] 500 Exception was thrown.

org.springframework.osgi.service.importer.ServiceProxyDestroyedException: service proxy has been destroyed at org.springframework.osgi.service.importer.support.internal.aop.ServiceDynamicInterceptor$ServiceLookUpCallback.doWithRetry(ServiceDynamicInterceptor.java:105)

..

..

..

at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)

at com.sun.proxy.$Proxy944.getBambooUser(Unknown Source)

Henrik Opel [Utoolity]

Yes, we just encountered such issues when using injected dependencies in Bamboo TaskConfigurator implementations in our own plugins. The problem does not seem to be tied to usage of a BambooUserManager dependency, rather any injected dependency from the host product will do.

As far as our current analysis goes, this is not tied to a specific Bamboo version, but triggered by a Disable/Enable cycle of the related Spring/OSGi contexts.

If our analysis is correct, you should be able to trigger the issue again by simply disabling and enabling the plugin once via UPM. A complete reinstall of the plugin fixes it again.

We reported this as a (likely) bug in Bamboo (BAM-14801), and we have come up with a possible workaround, but are waiting for confirmation of both the bug as well as the validity of our workaround.