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 com.sun.proxy.$Proxy944.getBambooUser(Unknown Source)
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.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot