The web application [ROOT] appears to have started a thread named [Abandoned connection cleanup thr

2019-05-06 11:26:40.552 WARN 29879 — [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘balanceController’: Unsatisfied dependency expressed through field ‘balanceService’; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name ‘balanceServiceImpl’: Unsatisfied dependency expressed through field ‘repayUserBalanceMapper’; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘repayUserBalanceMapper’ defined in URL [jar:file:/usr/local/xiaocaimi/xiaocaimi-repayment.jar!/BOOT-INF/lib/xiaocaimi-repayment-dao-1.0.0-SNAPSHOT.jar!/com/xiaocaimi/repayment/dao/RepayUserBalanceMapper.class]: Cannot resolve reference to bean ‘sqlSessionFactory’ while setting bean property ‘sqlSessionFactory’; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name ‘sqlSessionFactory’ defined in class path resource [com/xiaocaimi/repayment/config/MybatisConfig.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.apache.ibatis.session.SqlSessionFactory]: Factory method ‘sqlSessionFactory’ threw exception; nested exception is org.springframework.core.NestedIOException: Failed to parse mapping resource: ‘class path resource [mapper/RepayVipMapper.xml]’; nested exception is org.apache.ibatis.builder.BuilderException: Error parsing Mapper XML. Cause: org.apache.ibatis.builder.BuilderException: Error resolving class. Cause: org.apache.ibatis.type.TypeException: Could not resolve type alias ‘RepayVip’. Cause: java.lang.ClassNotFoundException: Cannot find class: RepayVip
2019-05-06 11:26:40.554 INFO 29879 — [ main] com.alibaba.druid.pool.DruidDataSource : {dataSource-1} closed
2019-05-06 11:26:40.558 INFO 29879 — [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2019-05-06 11:26:40.564 WARN 29879 — [ost-startStop-1] o.a.c.loader.WebappClassLoaderBase : The web application [ROOT] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
java.lang.Object.wait(Native Method)
java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:144)
com.mysql.cj.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:43)

在这里插入图片描述

原因在于RepayVip没有加前缀
在这里插入图片描述

Web应用程序 [root] 看上去启动了一个名为 [rxiosched] 的线程。根据描述,[rxiosched] 可能是一个与 RxJava 相关的调度器,用于管理响应式编程任务的线程调度。 RxJava 是一个用于构建基于事件流与数据流的异步和基于事件驱动的程序库,常用于开发响应式的Android应用。在RxJava中,任务可以通过不同的调度器在后台线程中运行,以避免阻塞主线程并提高应用程序的性能和响应性。 通过 [root] 应用程序启动了 [rxiosched] 线程,可能表明该应用程序正在使用RxJava库,并使用该调度器来处理异步任务。这可能意味着应用程序正在通过订阅观察者模式来处理事件,使任务在合适的时间和线程上执行。 这种线程调度的方法可以确保主线程不会被阻塞,这在开发需要进行网络请求或耗时操作的应用程序时尤为重要。它可以提供更好的用户体验,因为应用程序可以同时执行多个任务,并在数据准备好后及时响应用户输入。 就线程名称来说,[rxiosched] 或许是为了特定目的而命名的,我无法准确判断。但根据常规命名习惯,它可能与 RxJava 的 IO 调度器相关,用于在应用程序进行IO操作时进行线程调度。 总之,[root] 应用程序启动了 [rxiosched] 线程,这可能意味着应用程序正在使用RxJava库进行响应式编程,并使用调度器来管理任务线程。这种方法有助于提高应用程序的性能和响应性。
评论 4
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值