Bamboo failed to start after upgrading Bamboo 8.1 from 6.10.2
Asked by Mike James:

2022-02-09 21:37:00 Apache Commons Daemon procrun stderr initialized.  
09-Feb-2022 21:37:04.497 INFO \[main\] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache Tomcat Native library \[1.2.30\] using APR version \[1.7.0\].  
09-Feb-2022 21:37:04.497 INFO \[main\] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 \[true\], sendfile \[true\], accept filters \[false\], random \[true\].  
09-Feb-2022 21:37:04.497 INFO \[main\] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector \[false\], useOpenSSL \[true\]  
09-Feb-2022 21:37:04.513 INFO \[main\] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized \[OpenSSL 1.1.1k 25 Mar 2021\]  
09-Feb-2022 21:37:05.365 INFO \[main\] org.apache.coyote.http11.AbstractHttp11Protocol.configureUpgradeProtocol The \["http-nio-8085"\] connector has been configured to support HTTP upgrade to \[h2c\]  
09-Feb-2022 21:37:05.365 INFO \[main\] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler \["http-nio-8085"\]  
09-Feb-2022 21:37:06.226 INFO \[main\] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read  
09-Feb-2022 21:37:06.366 INFO \[main\] org.apache.catalina.startup.Catalina.load Initialization processed in 5404 ms  
09-Feb-2022 21:37:06.507 INFO \[main\] org.apache.catalina.core.StandardService.startInternal Starting service \[Catalina\]  
09-Feb-2022 21:37:06.507 INFO \[main\] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: \[Apache Tomcat/8.5.70\]  
09-Feb-2022 21:37:11.974 SEVERE \[Catalina-startStop-1\] org.apache.catalina.core.ContainerBase.startInternal A child container failed during start  
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component \[StandardEngine\[Catalina\].StandardHost\[localhost\].StandardContext\[\]\]  
at java.util.concurrent.FutureTask.report(FutureTask.java:122)  
at java.util.concurrent.FutureTask.get(FutureTask.java:192)  
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:942)  
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:833)  
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)  
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1427)  
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1417)  
at java.util.concurrent.FutureTask.run(FutureTask.java:266)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  
at java.lang.Thread.run(Thread.java:745)  
Caused by: org.apache.catalina.LifecycleException: Failed to start component \[StandardEngine\[Catalina\].StandardHost\[localhost\].StandardContext\[\]\]  
at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440)  
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198)  
... 6 more  
Caused by: java.lang.IllegalArgumentException: More than one fragment with the name \[spring_web\] was found. This is not legal with relative ordering. See section 8.2.2 2c of the Servlet specification for details. Consider using absolute ordering.  
at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2205)  
at org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2164)  
at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1083)  
at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:779)  
at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299)  
at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)  
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5130)  
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)  
... 6 more


Answers:
author: Mike James
body: This has been fixed. Atlassian support advised this is a known issue when using the windows installer to do an upgrade. The installer doesn't always clean-up old files from previous versions so the fix was to delete the install folder and re-install 8.1. After doing this...everything worked great.


author: Gonchik Tsymzhitov
body: Hi,

Could you check the logs earlier please?