My project is based on Springboot (1.5.21.RELEASE) and generates war and deployment in the physical Tomcat. I had the same problem and was solved with the following approach. Which means using absolute order. So you need to add a tag in your web file.xml inside the tag. If this is the case, you should use absolute correction of other answers or not include multiple copies of spring in some way. You can check if this is the case by going to tomcat/webapps/your_webapp/WEB-INF/lib, disabling all glasses and searching for « spring_web ». The tag was added to the web.xml worked for me. Will there be any other problems with the order? Your web .xml should look like this (added inside the web-app tag) After attempting to update Bamboo using Windows Setup, the process completes and nothing is written to the $BAMBOO_HOMElogsatlassian-bamboo.log file. An error: « More than one fragment named [spring_web] was found. » is logged in the $BAMBOO_INSTALLlogscatalina files* I had the same problem creating a war file with Maven because I did not clean up before packaging and Maven contained several versions of Spring JAR files from previous versions. This is not legal for relative orders. For more information, see Section 8.2.2 2c of the servlet specification. Consider using absolute order. org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2200) org.apache.tomcat.util.descriptor.web.WebXml.orderWebFragments(WebXml.java:2159) org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1124) org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:769) org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:299) org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94) to org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5181) to org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150).
11 more All these answers are excellent, but also check if « Apache CXF » lib is in your classpath, it seems to conflict with Spring Web 5.2.3, for me I temporarily deleted because I do not use it and now my project works fine. This issue may be caused by multiple versions of Spring, or because some dependencies were missing from your development environment. This issue is resolved by cleaning up Tomcat history or adding .xml web. Caused by: java.lang.IllegalArgumentException: Several fragments named [spring_web] were found. This is not legal for relative orders. For more information, see Section 8.2.2 2c of the servlet specification. Consider using absolute order. If you previously built the project with a different version, then changed the version and tried to build again, this exception is thrown.
You can delete the destination folder in your application. If you still get an exception, you can navigate to the project directory from terminal and type mvn clean install add tag to your website.xml just below the tag. It should work. Apparently, this is a change introduced in tomcat 7.0.93 FWIW (so it did not trigger this bug in older versions of tomcat 7) Alternatively, you can reinstall in a completely separate directory instead of reusing the old one. This issue was addressed by adding an absolute order of implementation descriptors. I did this after updating the Spring Framework version in a Maven project. I was finally able to solve the problem by running mvn cleanly, apparently the old POC Spring were picked up somewhere below the target. My project doesn`t contain multiple web fragments, so I don`t know what might be causing this problem. Whatever the webxml example, I don`t have a project with xmls. I have a project with features, feather boots I had the same problem and I solved it. Similar errors were received, but feather boots were not used. I used spring 3.x with Java 8.
If the above solutions don`t work, edit the JARs and check if these JARs are compatible with the Java version you are using or not. Spring 3.x is not compatible with Java 8. TBD Caused by: java.lang.IllegalArgumentException: Several fragments named [spring_web] were found. This is illegal in case of relative order error. Simply add the absolute command tag to your web folder.xml just below the file. That was it! The second solution is to simply check your dependencies to see if there are any Spring versions you rely on. NO. There was already a webxml. But no display name or absolute order, so I added them at the beginning. For me, this problem occurred when Tomcat was not installed correctly.
I reinstalled and updated the installation path: XXXX For me, this meant inserting « shaded glasses » that grouped spring copies into them. So, still « spring version », but several copies of the spring causes this. I had the same problem and I wanted to go to the cause. I knew that the fragment of the spring canvas glass was called « spring_web. » However, my source code did not have a « spring_web » fragment elsewhere. So I used a tool (jfind) to search for « spring_web » via an extended form of my EAR generated at the time of construction. Surprisingly, « spring_web » was found in the web fragment pot of another project generated at the time of construction. After correcting this second event, the problem was gone. So it seems to be due to a double « spring_web » fragment, and we only need one.
Note on platform: server and data center only. This article applies only to Atlassian products on server and data center platforms. Hi @aaronboss, sorry for the almost a year delay in the response. We have recently needed additional funds to support the open source activities of the MyStudies application. As for your initial question: I have a Spring Boot application that works well when I run it with Intellj`s built-in server. However, when I put it in a .war file and put it on Tomcat, I get the following error: Workaround: Exclude tomcat-embed-websocket dependency on spring-boot-starter-web in pom.xml. This method removes all Bamboo installation files related to $BAMBOO_INSTALL and from a new directory. If you are not clear about the difference between your Bamboo installation and your Bamboo Home directory, it may be useful to read the documentation, as it is very important that the Bamboo Home directory is not deleted: When I try to run « Debug LabKey Dev », everything seems to load fine until it comes to launching the Labkey component in Tomcat. The text was updated successfully, but the following errors occurred: www.oracle.com/technetwork/articles/javaee/javaee6overview-part2-136353.html I accidentally placed it in /WebContent (not/WEB-INF) and almost went crazy when I tried to apply some of the suggested solutions without success, the error message was exactly the same. Looks like you have two different versions of Spring, check your dependencies to see if you have a dependency on another version of Spring. For me, it was because of 2 spring-web jars, i.e.
spring-web-5.02-release.jar and spring-web-sources-5.02-release.jar in the build path. Removing spring-web-sources-5.02-release.jar resolves the issue. If you add all the jar files manually.jar you need to remove WEB-INF/lib/spring-web-5.2.9.RELEASE-sources or a similar JAR file (maybe your JAR version will be different). Once you have erased this glass, Tomcat will start working. Be sure to place web.xml in /WebContent/WEB-INF. To check if there is a Spring version dependency, just look at your dependencies. This error usually occurs when we have two copies of Spring in our container loaded by different class loaders (in my case, shared class loader and webapp class loader). If you upgrade Bamboo side-by-side with Windows Installer to the same installation folder as the previous installation, old files cannot be cleaned, resulting in duplicate libraries of different versions in the classpath. This error seems to occur after updating the project`s Spring framework, deleting the project history file in Tomcat Webapps may fix the problem. Check the effectiveness of the pompoms if you have a package that incorporates spring pots / classes, if so, remove it, you must use the one installed as the container package.