INFO: Deploying web application archive [F:\Tomcat\apache-tomcat-7.0.103-windows-x64\apache-tomcat-7.0.103\webapps\bos-web-0.0.1-SNAPSHOT.war]四月 24, 2020 3:09:45 下午 org.apache.catalina.core.ContainerBase addChildInternalSEVERE: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/bos-web-0.0.1-SNAPSHOT]] at org.apache.catalina.util.LifecycleBase.handleSubClassException(LifecycleBase.java:440) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:198) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1007) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:983) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:639) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2020) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)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.catalina.deploy.WebXml.orderWebFragments(WebXml.java:2338) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1279) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:888) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:388) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5545) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) ... 11 more四月 24, 2020 3:09:45 下午 org.apache.catalina.startup.HostConfig deployWARSEVERE: 部署 Web 应用程序 archive [F:\Tomcat\apache-tomcat-7.0.103-windows-x64\apache-tomcat-7.0.103\webapps\bos-web-0.0.1-SNAPSHOT.war] 时出错java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/bos-web-0.0.1-SNAPSHOT]] at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:1011) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:983) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:639) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1127) at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:2020) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)四月 24, 2020 3:09:45 下午 org.apache.catalina.startup.HostConfig deployWAR

CodePudding user response:

May be your configuration path problem, and then look at your project in the default URL

CodePudding user response:

reference 1/f, extremely apes response:

may be you configuration path problem, and look at your project in the default URL

Maven after the test, there are two jars is invalid, can affect?

CodePudding user response:

refer to the second floor gyh_98716 response:

Quote: refer to 1st floor extremely apes response:

may be you configuration path problem, and look at your project in the default URL

Maven after the test, there are two jars is invalid, can affect?

Since project rev, should have no influence, what is your front page? jsp? You can right-click the debug to start the first find a page and see what path is,,,, or go to tomcat application deployment in the context of the path is/bas - web

CodePudding user response:

reference 3 floor extremely apes response:

Quote: refer to the second floor gyh_98716 response:

Quote: refer to 1st floor extremely apes response:

may be you configuration path problem, and look at your project in the default URL

Maven after the test, there are two jars is invalid, can affect?

Since project rev, should have no influence, what is your front page? jsp? You can right-click the debug to start the first find a page and see what path is,,,, or go to deployment of the application in tomcat is the context path/bas - web

There is no deployment in tomcat this file? In eclipse?

CodePudding user response:

nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull