Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bamboo does not start up (Critical Business Impact)


Hello, yesterday we encountered an error where it appears the bamboo service hung.  Stopping it and attempting to restart it now results in the service terminating itself due to what appears to be an issue loading the cucumber plugin (see error below).

No changes have been made from a configuration standpoint, and even restarting the physical server itself, and starting the bamboo service fresh results in the same error (app is definitely not being deployed twice).

org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter struts-prepare
The package name 'cucumberPlugin' at location null is already been used by another package at location null
at org.apache.struts2.dispatcher.Dispatcher.init(
at com.atlassian.bamboo.ww2.StrutsPrepareFilter.init(
at org.apache.catalina.core.ApplicationFilterConfig.initFilter(
at org.apache.catalina.core.ApplicationFilterConfig.getFilter(
at org.apache.catalina.core.ApplicationFilterConfig.<init>(
at org.apache.catalina.core.StandardContext.filterStart(
at org.apache.catalina.core.StandardContext.startInternal(
at org.apache.catalina.util.LifecycleBase.start(
at org.apache.catalina.core.ContainerBase$
at org.apache.catalina.core.ContainerBase$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$
Caused by: The package name 'cucumberPlugin' at location null is already been used by another package at location null
at com.opensymphony.xwork2.config.impl.DefaultConfiguration.addPackageConfig(


Seems like a clear enough error, but I am not presently seeing what is causing it.  Please let me know what other information I can provide to help you assist with resolution of this issue. Any assistance you can provide is greatly appreciated, as having Bamboo down has a very significant negative impact on our business.  Thanks.


EDIT: My apologies, I was trying to submit a support ticket as opposed to posting in the community, but any assistance anyone can provide is appreciated all the same.  Thanks.

2 answers

1 accepted

0 votes
Answer accepted

This is what happens when you go 30+ hours without sleep.  Think I fixed the issue.  The server was not shut down cleanly, and there were duplicates of the cucumber .jar in the data and data/caches directories.  Cleaning those up obviously fixes the problem of the package name trying to load more than once and failing.  Hopefully this (pretty obvious) answer helps someone else.  Thanks.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events