report-findbugs-2.0.9.jar
Hello,
I installed a 30-day trial of report-findbugs-2.0.9.jar last week, but some days later, the machine my bamboo server runs on was patched (O/S patch) by our IT Team, and then bamboo didn't come up any longer.
The error I received in the bamboo log related to this, I believe, was:
2019-11-21 11:11:12,116 ERROR [localhost-startStop-1] [Dispatcher] Dispatcher initialization failed The package name 'findbugsPlanBuildSummaryView' at location null is already been used by another package at location null at com.opensymphony.xwork2.config.impl.DefaultConfiguration.addPackageConfig(DefaultConfiguration.java:124) at com.atlassian.bamboo.plugin.xwork.XWorkModuleDescriptor.loadPackages(XWorkModuleDescriptor.java:83) at com.opensymphony.xwork2.config.impl.DefaultConfiguration.reloadContainer(DefaultConfiguration.java:196) at com.opensymphony.xwork2.config.ConfigurationManager.reload(Configuration
I am running Bamboo 6.9.1 on a Linux oel6 machine.
I am using Java JDK 1.8.0_231 (also tried 1.8.0_221).
to fix it, I had to do the following:
I moved plugin_3687578157848474927_report-findbugs-2.0.9.jar from /nif/builds/bamboo/plugins to /nif/builds/bamboo/old/plugins
(bamboo-home = /nif/builds/bamboo).
I had no indication the addon/plugin would cause a problem - it seemed to install ok, and I put the generated temporary license in when I installed it.
Atlassian graciously helped me troubleshoot the problem on issue/ticket: BSP-44614 .
I am now a bit leary of reinstalling unless I hear more.
Thanks much,
Dan
Comments (3)
-
repo owner -
repo owner No further update here, closing.
Please reopen if needed! -
repo owner - changed status to resolved
Closing here as problem is fixed hopefully.
- Log in to comment
Hi Dan,
thanks for the information.
I think contacting Atlassian in the first place was a good choice. Can you please paste the URL of the ticket BSP-44614?
I can understand you are afraid of reinstalling the addon. As I have not heard of such a problem in 3 ½ years (first supported Bamboo was v5.10), though I cannot guarantee it, I think you are safe in reinstalling the addon.
With kind regards,
Markus