大抵是最全的Tomcat启动报A child container failed during start问题解决

已于 2023-04-05 15:58:38 修改
阅读量3k 收藏 3
点赞数 4
文章标签： tomcat java jvm xml
于 2023-04-05 15:54:27 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/m0_65836249/article/details/129971753
版权

我们首先来看看报错

java.net.BindException: Address already in use: JVM_Bind <null>:8080
	at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:407)
	at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:623)
	at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)
	at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
	at org.apache.catalina.connector.Connector.initInternal(Connector.java:981)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
	at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
	at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
	at org.apache.catalina.startup.Tomcat.start(Tomcat.java:341)
	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1238)
	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:592)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
Caused by: java.net.BindException: Address already in use: JVM_Bind
	at java.net.DualStackPlainSocketImpl.bind0(Native Method)
	at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)
	at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)
	at java.net.ServerSocket.bind(ServerSocket.java:375)
	at java.net.ServerSocket.<init>(ServerSocket.java:237)
	at java.net.ServerSocket.<init>(ServerSocket.java:181)
	at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)
	at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:394)
	... 36 more
四月 05, 2023 3:42:30 下午 org.apache.catalina.core.StandardService initInternal
严重: Failed to initialize connector [Connector[HTTP/1.1-8080]]
org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-8080]]
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:106)
	at org.apache.catalina.core.StandardService.initInternal(StandardService.java:559)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
	at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:814)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:139)
	at org.apache.catalina.startup.Tomcat.start(Tomcat.java:341)
	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1238)
	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:592)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed
	at org.apache.catalina.connector.Connector.initInternal(Connector.java:983)
	at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)
	... 31 more
Caused by: java.net.BindException: Address already in use: JVM_Bind <null>:8080
	at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:407)
	at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:623)
	at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:434)
	at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
	at org.apache.catalina.connector.Connector.initInternal(Connector.java:981)
	... 32 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
	at java.net.DualStackPlainSocketImpl.bind0(Native Method)
	at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)
	at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
	at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)
	at java.net.ServerSocket.bind(ServerSocket.java:375)
	at java.net.ServerSocket.<init>(ServerSocket.java:237)
	at java.net.ServerSocket.<init>(ServerSocket.java:181)
	at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)
	at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:394)
	... 36 more
四月 05, 2023 3:42:30 下午 org.apache.catalina.core.StandardService startInternal
信息: Starting service Tomcat
四月 05, 2023 3:42:30 下午 org.apache.catalina.core.StandardEngine startInternal
信息: Starting Servlet Engine: Apache Tomcat/7.0.47
四月 05, 2023 3:42:31 下午 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[Tomcat].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:1123)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Tomcat].StandardHost[localhost].StandardContext[]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	... 6 more
Caused by: java.lang.IllegalArgumentException: The servlets named [com.anglyao.ServletDemo2] and [com.anglyao.ServletDemo3] are both mapped to the url-pattern [/demo2] which is not permitted
	at org.apache.catalina.deploy.WebXml.addServletMapping(WebXml.java:335)
	at org.apache.catalina.startup.ContextConfig.processAnnotationWebServlet(ContextConfig.java:2466)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2148)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2109)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2102)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2102)
	at org.apache.catalina.startup.ContextConfig.processAnnotationsFile(ContextConfig.java:2102)
	at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1293)
	at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:878)
	at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:376)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
	at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5322)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 6 more
四月 05, 2023 3:42:31 下午 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[Tomcat].StandardHost[localhost]]
	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:1123)
	at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:302)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:732)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	at org.apache.catalina.startup.Tomcat.start(Tomcat.java:341)
	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.startContainer(AbstractRunMojo.java:1238)
	at org.apache.tomcat.maven.plugin.tomcat7.run.AbstractRunMojo.execute(AbstractRunMojo.java:592)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:957)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:289)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:193)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347)
	at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Tomcat].StandardHost[localhost]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.catalina.LifecycleException: A child container failed during start
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1131)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
	... 6 more

这样的报错信息不光臭长，而且极难理解，所以给大家列出几个常见的这种报错的解决方法：

1、servlet-api包冲突

出现这个问题的原因是导入了servlet-api包，与tomcat7的依赖包servlet-api冲突，可以检查pom.xml是否导入javax.servlet-api

加上<scope>provided</scope>之后

  <dependencies>
    <dependency>
      <groupId>javax.servlet</groupId>
      <artifactId>javax.servlet-api</artifactId>
      <version>3.1.0</version>
      <scope>provided</scope>
    </dependency>

再次运行，成功启动

2、不排除是版本问题，更换servlet版本试一试（但是我还没有遇到过）

3、冗余的配置或多余的代码

检查pom.xml中多余的配置，将多余的配置注释掉

4、路径重复

这一点也是最常见的错误，像我就是在学习的时候，图方便直接copy代码，导致新文件的

@WebServlet注释里的urlPatterns重复与老文件urlPatterns重复，更换一下路径名即可。

也有可能是你的urlPattens路径中的路径不对，好好检查一下。

RicardoLou
关注
  • 4
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 2
    评论
stc单片机烧写问题
08-28
常常在贴吧和知道上看到求助此类问题的人，大家的解答大抵是说什么串口驱动安装没啊、型号选对没有啊、冷启动没有啊之类的，其实，真正遇到烧写不了程序的人大抵不是因为这些问题，根据我的总结，可能的原因将在本文...
完美解决关于禁止ViewPager预加载的相关问题
01-05
相信用过ViewPager的人大抵都有遇到过这种情况，网上的解决办法也就那么几个，终于在我自己不断试验之下，完美解决了（禁止了）ViewPager的预加载。 好了，首先来说明一下，什么是ViewPager的预加载：ViewPager有一...
Tomcat启动时报错:A child container failed during start解
m0_74635878的博客
05-10 1410
这里的demo3和demo4的路径名相同才导致报错 “A child container failed during start”有没有，没有的话tomcat也是会报“A child container failed during start”操作：添加maven helper插件后，右键→run maven→clean。解决方法：执行clean命令，然后重新启动项目。不是这个问题的话就要看看pom.xml了。点击红框内，查看该项目内的所有路径名称。修改完之后，就不会报错了。希望以上内容对大家有所帮助。
A child container failed during start之解决方法
qq_42680327的博客
11-09 1411
A child container failed during start之解决方法
springboot启动报错org.apache.catalina.core.ContainerBase : A child container failed during start
lewandowskii的博客
07-09 9544
IDEA springboot项目启动报错org.apache.catalina.core.ContainerBase : A child container failed during start出错起因解决思路解决方法 出错起因 笔者将一个springboot项目部分代码复制到另一个springboot项目后，运行报错“A child container failed during start” 解决思路 笔者在搜索众多关于本问题的解决方法后仍没有成功解决。但是初步找到了思路：就是从其他项目导入的代
tomcat用startup.bat直接启动几秒后自动退出启动失败、org.apache.catalina.core.ContainerBase.startInternal A child conta
Teachmepatiently的博客
08-01 749
tomcat用startup.bat直接启动几秒后自动退出启动失败、org.apache.catalina.core.ContainerBase.startInternal A child conta
启动Tomcat时报错：A child container failed during start
你若盛开，清风自来。
04-22 479
是一样的，导致出现映射冲突。
我大抵是卷上瘾了，横竖睡不着！竟让一个Bug，搞我两次！.doc
07-11
这个问题的根源在于 selectKey 的配置问题。 首先，让我们来了解一下 Mybatis 的处理过程。Mybatis 的处理过程可以分为两个大部分：解析和使用。解析的时候，把 Mapper XML 中的 insert 标签语句解析出来，同时解析...
跟我学VB—VB无解问题与API的解决方案
04-29
PC 2 月号， 属於新春期间， 笔者想来点轻松而又实用的东西，所以特别挑选读者问过而 VB 无法解决的问题， 以 Windows API 来加以解决，除了第 4 则与第 15 则之外， 这些解决方案大抵上没有太艰涩的技术， 您只要...
大抵观书先须熟读，使其言......阅读答案_大抵观书先须熟读.docx
11-26
大抵观书先须熟读，使其言......阅读答案_大抵观书先须熟读.docx
报错：（严重: A child container failed during start）（Server component failed to start so Tomcat is unable）
_夜渐凉
08-03 4660
启动Java Web项目时提示错误：A child container failed during start. 提示：A child container failed during start 从来都不是问题的根本原因，需要往下看Caused by的内容。 启动Java Web项目时提示错误：The required Server component failed to start so To...
Javaweb项目，无法启动tomcat（报错：A child container failed during start）
hugh 的博客
04-20 6万+
启动Java Web项目时，发现tomcat无法启动，并eclipse弹出错误提示框，localhost tomcat is faild之类的再看控制台的输出信息，发现几个严重错误，本着 最先解决 第一个问题的 原则，看到第一个的提示错误如下：提示错误：A child Container failed during start 完整错误信息如下：严重: A child container faile
tomcat奇怪错误之A child container failed during start
热门推荐
Kaiwii的专栏
08-23 16万+
错误详情： 严重: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[loca
启动Tomcat报错：A child container failed during start
问知青云路的博客
05-12 1万+
在之前的工作和学习当中，有碰到过很多未知的，在当时看来十分令人疑惑的问题。当时的解决手段简单粗暴，就是直接百度，搜到对应的解决方案，直接抄过来试试，不行再换，直到问题消失，程序可以正常跑了，立马就不管不问了，认为解决了问题。其实这样很不好，一方面是问题消失了，但并不是真正的被解决了。另一方面则是，自己对这个问题没有更深的感悟和记录，以后碰到同样或者类似的问题，还是没有掌握解决的方法。只依靠百度搜索...
tomcat关闭重启遇到A child container failed during start问题
huangbaokang的博客
09-29 1636
tomcat重启的时候遇到了如下错误： java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/chapt...
A child container failed during异常解决
toString的博客
12-14 705
今天创建maven项目的时候启动时报的这个异常，主要时后面的 Caused by: java.lang.ClassCastException:org.springframework. 此类问题的多半是web.xml配置有问题，或者是pom.xml中的jar包冲突。根据关键信息org.springframework.web.SpringServletContainerInitializer
tomcat 启动报错：严重: A child container failed during start
qq_43614498的博客
07-07 568
tomcat 启动报错：严重: A child container failed during start 严重: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].Sta
idea+springboot启动报错 ERROR org.apache.catalina.core.ContainerBase
追求卓越583的博客
08-18 4241
idea+springboot启动报错 ERROR org.apache.catalina.core.ContainerBase
maven 使用tomcat插件启动报错 A child container failed during start
hanzl1的博客
07-07 4285
1.出现这个的原因，我查了好多，一般是处在 javax这个jar包上。首先检查pom文件是否存在  &lt;dependency&gt; &lt;groupId&gt;javax.servlet&lt;/groupId&gt; &lt;artifactId&gt;servlet-api&lt;/artifactId&gt; &lt;scope&gt;provided&lt;/scope&
请写一个JavaScript代码请求url返回显示{ "data": { "visionProfile": { "__typename": "VisionProfileResult", "hostName": "public-bjzey-c11-kce-node899.idczw.hb1.kwaidc.com", "result": 1, "userProfile": { "__typename": "VisionUserProfile", "isFollowing": false, "profile": { "gender": "F", "headurl": "https://p5-pro.a.yximgs.com/uhead/AB/2023/03/17/15/BMjAyMzAzMTcxNTI3NTZfNjcyNjMyNTExXzFfaGQ1MTdfNzAx_s.jpg", "user_id": "3xv4qdp8jwrgb8i", "user_name": "大抵是风吹过ˡᵃ", "user_text": "从前车马很慢 一生只够爱一个人" } } } } }这些的代码
最新发布
06-10
由于浏览器的同源策略限制，跨域请求需要使用JSONP或CORS技术。下面是一个使用CORS获取数据的示例代码： ```javascript ... method: 'GET', headers: { 'Content-Type': 'application/json' } ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值