INFO: Initializing Spring root WebApplicationContext log4j:3个WARN卡死的解决

最新推荐文章于 2022-03-24 11:49:08 发布
原创 最新推荐文章于 2022-03-24 11:49:08 发布 · 3.6k 阅读 · 3 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#spring #log4j #框架 #tomcat

本文介绍了一种常见的情况：启动Tomcat时程序卡在特定阶段且无任何输出的情况。文章详细解释了这一现象背后的原因，并提供了解决方案，包括如何正确配置log4j.properties文件以捕获错误日志。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

启动tomcat加载到这里卡死，没有任何输出，如下

INFO: Initializing Spring root WebApplicationContext
log4j:WARN No appenders could be found for logger (org.springframework.web.context.ContextLoader).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

等很长时间没有反应，这时很大可能是后台已经报错了，可能是文件加载过成功出现了死循环，导致启动不了，

ssm框架中可能是spring报错，然而因为没有配置log4j.properties文件导致日志没有输出，从而看不到报错，此时

需要增加log4j.properties文件，这个log4j文件只要放在src目录下就可以，log4j组件会自动加载log4j.properties文件，

看到报错后可以针对报错信息进行修改。

附上一个比较通用的log4j.properties文件(点击下载)



Initializing ExecutorService ‘applicationTaskExecutor‘
王大师企业官方博客
11-16 6213
Initializing ExecutorService 'applicationTaskExecutor'报错代码解决方案 报错代码 "C:\Program Files\Java\jdk1.8.0_131\bin\java.exe" -XX:TieredStopAtLevel=1 -noverify -Dspring.output.ansi.enabled=always -Dcom.sun.management.jmxremote -Dspring.jmx.enabled=true -Dspring.li
关于Initializing Spring root WebApplicationContext问题
xiaoguaihu12的博客
02-08 2606
2017-02-08 遇到问题:从中午掉到晚上19:50 解决             系统环境:win10+Eclipse(Mars)+JDK(1.7)+Maven+Tomcat7依赖插件+mysql5.7 Maven项目,使用逆向工程生成的,dao接口,mapper映射,pojo实体类             使用在manager聚合工程中配置的tomcat插件   
Web服务器启动（ssh）信息: Initializing Spring root WebApplicationContext
samll leaf
03-08 848
web 服务器启动 Tomcat 信息: Initializing Spring root WebApplicationContext 一直停在这里不动，我当时纠结了很久。使用的是常见的Struts2+hibernate+spring 1）首先产看配置是否出错，applicationContext.xml是否有问题 2）XXX.hbm.xml是否写错 3）jar包是否冲突（ssh整
SSH或者SSM项目启动时候一直卡在“信息: Initializing Spring root WebApplicationContext“ 解决办法
qq_35639030的博客
05-12 6964
首先看到的是卡在了“Initializing Spring root WebApplicationContext”，提取关键字所以第一个原因就是你的Spring配置文件出了问题，一般为映射文件的问题。但是大多数时候我们是没有动Spring配置文件，就是长时间不用项目，当用的时候启动时时候启动不起来。这时候就是第二个原因。你的数据库有问题了。博主毕设答辩前一天，系统突然出现了这个问题。找了好多网上资...
一直卡在 Initializing Spring embedded WebApplicationContext
web15085599741的博客
03-24 1234
描述：Spring Boot项目启动不了，一直卡在 Initializing Spring embedded WebApplicationContext，看启动日志，找到 ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console… ，其实是 pom 依赖包的问题，因为项目.
信息: Initializing Spring root WebApplicationContext
iteye_12242的博客
11-19 100
在使用SSI进行开发过程中，如果mybatis中mapper的xml中sql等有错，则会一直停在这个地方，但是mybatis不会报错。这真是非常郁闷啊,找到最近修改的xml认真检查原因...
/\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.5.9) 2025-04-02 05:58:52.097 INFO 6272 --- [ main] com.example.SpringbootApplication : Starting SpringbootApplication using Java 1.8.0_381 on LAPTOP-JK6P0P12 with PID 6272 (D:\酒店预订\xm-hotel-manager\springboot\target\classes started by hp in D:\酒店预订\xm-hotel-manager) 2025-04-02 05:58:52.098 INFO 6272 --- [ main] com.example.SpringbootApplication : No active profile set, falling back to default profiles: default 2025-04-02 05:58:52.719 INFO 6272 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 9091 (http) 2025-04-02 05:58:52.724 INFO 6272 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] 2025-04-02 05:58:52.724 INFO 6272 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.56] 2025-04-02 05:58:52.765 INFO 6272 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext 2025-04-02 05:58:52.765 INFO 6272 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 642 ms
最新发布
04-03
2025-04-02 05:58:52.765 INFO 6272 --- [main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 642 ms ``` - **上下文加载**：Spring容器初始化耗时`642ms`...
____ _ __ _ _ /\ / ’ __ _ () __ __ _ \ \ \ ( ( )__ | '_ | '| | ’ / ` | \ \ \ \/ )| |)| | | | | || (| | ) ) ) ) ’ || .__|| ||| |_, | / / / / =========||==============|/=//// :: Spring Boot :: (v2.2.2.RELEASE) 2025-03-30 22:24:27.599 INFO 6052 — [ main] com.SpringbootSchemaApplication : Starting SpringbootSchemaApplication on DESKTOP-IBCAV8B with PID 6052 (D:\code\springboot55415\target\classes started by 卢民艺 in D:\code\springboot55415) 2025-03-30 22:24:27.601 INFO 6052 — [ main] com.SpringbootSchemaApplication : No active profile set, falling back to default profiles: default 2025-03-30 22:24:30.883 INFO 6052 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http) 2025-03-30 22:24:30.888 INFO 6052 — [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] 2025-03-30 22:24:30.888 INFO 6052 — [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.29] 2025-03-30 22:24:30.955 INFO 6052 — [ main] o.a.c.c.C.[.[.[/springboot55415] : Initializing Spring embedded WebApplicationContext 2025-03-30 22:24:30.955 INFO 6052 — [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 3309 ms 2025-03-30 22:24:31.093 INFO 6052 — [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting… 2025-03-30 22:24:31.339 INFO 6052 — [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed. 2025-03-30 22:24:32.210 INFO 6052 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ‘/springboot55415’ 2025-03-30 22:24:32.212 INFO 6052 — [ main] com.SpringbootSchemaApplication : Started SpringbootSchemaApplication in 4.919 seconds (JVM running for 5.924)
03-31
Initializing Spring embedded WebApplicationContext Root WebApplicationContext: initialization completed in 3309 ms ``` - **上下文路径**：默认路径为`/springboot55415`，访问接口时需包含此路径（如`...
2025.03.17 10:09:36|INFO |org.apache.juli.logging.DirectJDKLog|log()|173|Starting Servlet engine: [Apache Tomcat/9.0.33] 2025.03.17 10:09:36|INFO |org.apache.juli.logging.DirectJDKLog|log()|173|Initializing Spring embedded WebApplicationContext 2025.03.17 10:09:36|INFO |org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext|prepareWebApplicationContext()|284|Root WebApplicationContext: initialization completed in 2729 ms 2025.03.17 10:09:36|DEBUG|io.micrometer.core.util.internal.logging.InternalLoggerFactory|newDefaultFactory()|61|Using SLF4J as the default logging framework 2025.03.17 10:09:36|ERROR|org.springframework.boot.web.embedded.tomcat.TomcatStarter|onStartup()|61|Error starting Tomcat context. Exception: org.springframework.beans.factory.BeanCreationException. Message: Error creating bean with name 'servletEndpointRegistrar' defined in class path resource [org/springframework/boot/actuate/autoconfigure/endpoint/web/ServletEndpointManagementContextConfiguration$WebMvcServletEndpointManagementContextConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.endpoint.web.ServletEndpointRegistrar]: Factory method 'servletEndpointRegistrar' threw exception; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'healthEndpoint' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Unsatisfied dependency expressed through method 'healthEndpoint' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'healthContributorRegistry' defined in class path resource [org/springframework/boot/actuate/autoconfigure/health/HealthEndpointConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.health.HealthContributorRegistry]: Factory method 'healthContributorRegistry' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dbHealthContributor' defined in class path resource [org/springframework/boot/actuate/autoconfigure/jdbc/DataSourceHealthContributorAutoConfiguration.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.actuate.health.HealthContributor]: Factory method 'dbHealthContributor' threw exception; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'scopedTarget.dataSource' defined in class path resource [org/springframework/boot/autoconfigure/jdbc/DataSourceConfiguration$Hikari.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.zaxxer.hikari.HikariDataSource]: Factory method 'dataSource' threw exception; nested exception is org.springframework.boot.autoconfigure.jdbc.DataSourceProperties$DataSourceBeanCreationException: Failed to determine a suitable driver class 2025.03.17 10:09:36|INFO |org.apache.juli.logging.DirectJDKLog|log()|173|Stopping service [Tomcat] 2025.03.17 10:09:36|WARN |org.springframework.context.support.AbstractApplicationContext|refresh()|558|Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat 2025.03.17 10:09:36|INFO |org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener|logMessage()|136|
03-18
另外，如果使用的是Spring Boot的自动配置，可能需要确保DataSource的配置是正确的，或者是否有多个数据源配置导致冲突。有时候排除自动配置也可能引起问题，需要检查是否有不必要的排除项。 用户可能需要一步步...
06:53:37.232 [main] INFO c.r.s.RuoYiSystemApplication - [logStartupProfileInfo,638] - The following 1 profile is active: "dev" 06:53:39.561 [main] INFO o.a.c.h.Http11NioProtocol - [log,173] - Initializing ProtocolHandler ["http-nio-9201"] 06:53:39.566 [main] INFO o.a.c.c.StandardService - [log,173] - Starting service [Tomcat] 06:53:39.566 [main] INFO o.a.c.c.StandardEngine - [log,173] - Starting Servlet engine: [Apache Tomcat/9.0.96] 06:53:39.678 [main] INFO o.a.c.c.C.[.[.[/] - [log,173] - Initializing Spring embedded WebApplicationContext 06:53:39.836 [main] WARN c.b.d.d.DynamicRoutingDataSource - [afterPropertiesSet,243] - dynamic-datasource initial loaded [0] datasource,Please add your primary datasource or check your configuration 06:53:40.806 [main] WARN o.s.b.w.s.c.AnnotationConfigServletWebServerApplicationContext - [refresh,599] - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'sysDictDataController': Unsatisfied dependency expressed through field 'dictTypeService'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sysDictTypeServiceImpl': Invocation of init method failed; nested exception is org.apache.ibatis.binding.BindingException: Invalid bound statement (not found): com.ruoyi.system.mapper.SysDictDataMapper.selectDictDataList 06:53:40.826 [main] INFO c.b.d.d.DynamicRoutingDataSource - [destroy,215] - dynamic-datasource start closing .... 06:53:40.826 [main] INFO c.b.d.d.DynamicRoutingDataSource - [destroy,219] - dynamic-datasource all closed success,bye 06:53:40.828 [main] INFO o.a.c.c.StandardService - [log,173] - Stopping service [Tomcat] 06:53:40.915 [main] ERROR o.s.b.SpringApplication - [reportFailure,818] - Application run failed org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'sysDictDataController': Un
03-12
首先，用户使用了dynamic-datasource-spring-boot-starter这个多数据源启动器，引用[2]提到这个工具可以快速集成多数据源。可能的问题点包括数据源配置错误、MyBatis接口绑定问题或者组件扫描的问题。 第一步，检查...
myeclipse启动tomcat停在 信息: Initializing Spring root WebApplicationContext
玛尼的博客
05-13 676
信息: Initializing Spring root WebApplicationContext 解决方法： 关闭tomcat后在deploy处remove掉刚修改的项目，重启tomcat重新add进tomcat中，deploy。 成功！
一直停留“信息: Initializing Spring root WebApplicationContext”
mynameishxf的专栏
08-31 3880
启动tomcat一直停留在上面的这行，可能是内部错误，没有答应出来。请修改Logger级别为debug
Initializing Spring root WebApplicationContext
啊哈程序
06-14 2476
某日,再次启动项目，spring一直停在这一句:  Java代码   Initializing Spring root WebApplicationContext   就这样，一直不动，随便你等多久，就是不会往下走半步，网上搜了一堆，全是些没用的东西，你抄我我抄你，突然，项目组里其他成员跟我说数据库的IP 和端口变了，我擦，是不是这里，一看，果然是因为这个
SSH项目tomcat启动停在Initializing Spring root WebApplicationContext
it44809252的博客
11-21 689
一、 http://www.iteye.com/topic/965566  某日,再次启动项目，spring一直停在这一句:  Java代码   Initializing Spring root WebApplicationContext   就这样，一直不动，随便你等多久，就是不会往下走半步，网上搜了一堆，全是些没用的东西，你抄我我抄你，突然，项目组里其...
项目卡在Initializing Spring root WebApplicationContext
点点滴滴的博客
04-01 794
1、没有连接好数据库 2、在确保1正确的情况下，请查看application.xml里面的包扫描，如service包的扫描路径，serviceImp、mapper、entity等
tomcat 启动时 Initializing Spring root WebApplicationContext停止启动
ch847808805的专栏
05-02 7907
SSH 框架整合。tomcat 容器初次启动可以正常加载spring信息，以后在重新启动容器就会卡在 Initializing Spring root WebApplicationContext 停止运行，其实不是停止只是spring加载太忙，问题出在struts上，现在很多开发工作在做ssh整合的时候会自动帮你天下需要的jar文件，会多jar都是有问题了，或是有冲突的，所以我们要我却掉一些没
spring+mybatis项目启动报错Initializing Spring root WebApplicationContext
weixin_34273046的博客
04-23 169
这个问题很怪异，各种各样的情况都会导致这个问题的出现，主要是由于sping加载读取配置文件的时候出了问题。我在处理mybatis的时候出现了这个问题，后来排查发现，在mybatis的配置文件中如果有大于(>)和小于(<)的情况下需要加<![CDATA[符号标识。 出问题的情况如下： where rn > (#{pageNumber,jdbcType=DECIMA...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值