java异常-SpringBoot-

简介: java异常-SpringBoot-

异常



  WARN [admin,,,] [main] o.a.c.loader.WebappClassLoaderBase.log:173 The web application [ROOT] appears to have started a thread named [OkHttp ConnectionPool] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@11.0.6/java.lang.Object.wait(Native Method)
 java.base@11.0.6/java.lang.Object.wait(Object.java:462)
 app//okhttp3.ConnectionPool$1.run(ConnectionPool.java:67)
 java.base@11.0.6/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 java.base@11.0.6/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 java.base@11.0.6/java.lang.Thread.run(Thread.java:834)

  WARN [admin,,,] [main] o.a.c.loader.WebappClassLoaderBase.log:173 The web application [ROOT] appears to have started a thread named [Okio Watchdog] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@11.0.6/java.lang.Object.wait(Native Method)
 java.base@11.0.6/java.lang.Object.wait(Object.java:462)
 app//okio.AsyncTimeout.awaitTimeout(AsyncTimeout.java:361)
 app//okio.AsyncTimeout$Watchdog.run(AsyncTimeout.java:312)

 WARN [admin,,,] [main] o.a.c.loader.WebappClassLoaderBase.log:173 The web application [ROOT] appears to have started a thread named [redisson-netty-2-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@11.0.6/sun.nio.ch.EPoll.wait(Native Method)
 java.base@11.0.6/sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:120)
 java.base@11.0.6/sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:124)
 java.base@11.0.6/sun.nio.ch.SelectorImpl.select(SelectorImpl.java:136)
 app//io.netty.channel.nio.SelectedSelectionKeySetSelector.select(SelectedSelectionKeySetSelector.java:62)
 app//io.netty.channel.nio.NioEventLoop.select(NioEventLoop.java:807)
 app//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:457)
 app//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
 app//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
 app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
 java.base@11.0.6/java.lang.Thread.run(Thread.java:834)
2021-07-10 23:05:42.297+0800  WARN [admin,,,] [main] o.a.c.loader.WebappClassLoaderBase.log:173 The web application [ROOT] appears to have started a thread named [redisson-netty-2-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.base@11.0.6/java.util.zip.Inflater.inflateBytesBytes(Native Method)
 java.base@11.0.6/java.util.zip.Inflater.inflate(Inflater.java:385)
 java.base@11.0.6/java.util.zip.InflaterInputStream.read(InflaterInputStream.java:153)
 java.base@11.0.6/jdk.internal.loader.Resource.getBytes(Resource.java:124)
 java.base@11.0.6/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:797)
 java.base@11.0.6/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:698)
 java.base@11.0.6/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:621)
 java.base@11.0.6/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:579)
 java.base@11.0.6/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
 java.base@11.0.6/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
 app//io.netty.util.Recycler$Stack.newWeakOrderQueue(Recycler.java:691)
 app//io.netty.util.Recycler$Stack.pushLater(Recycler.java:674)
 app//io.netty.util.Recycler$Stack.push(Recycler.java:633)
 app//io.netty.util.Recycler$DefaultHandle.recycle(Recycler.java:224)
 app//io.netty.channel.AbstractChannelHandlerContext$WriteTask.recycle(AbstractChannelHandlerContext.java:1115)
 app//io.netty.channel.AbstractChannelHandlerContext$WriteTask.run(AbstractChannelHandlerContext.java:1092)
 app//io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)
 app//io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)
 app//io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:500)
 app//io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
 app//io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
 app//io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
 java.base@11.0.6/java.lang.Thread.run(Thread.java:834)



解决

不要心急,多半是映射问题导致,差一下 dao 到 xml 配置。

目录
相关文章
|
3天前
|
Java 开发者 UED
【实战宝典】Java异常处理大师级教程:throws关键字,让异常声明成为你的专属标签!
【6月更文挑战第19天】在Java中,`throws`关键字是异常处理的关键,它提升了方法签名的透明度和代码质量。不使用`throws`时,未捕获的异常可能导致程序崩溃。例如,`readFileContent`方法若不声明`throws IOException`,则隐藏了可能的风险。而明确声明如`throws IOException`,提醒调用者需处理异常,增强代码稳定性。
|
2天前
|
安全 算法 Java
在Spring Boot项目中集成Jasypt(Java Simplified Encryption)
在Spring Boot项目中集成Jasypt(Java Simplified Encryption)
18 7
|
3天前
|
Java 程序员 数据库连接
处理Java异常
处理Java异常
12 4
|
4天前
|
前端开发 Java
【技术进阶】Java高手都在用的秘籍:自定义异常,让错误信息说话!
【6月更文挑战第19天】在Java中,自定义异常提升代码可读性和可维护性,提供针对特定错误的定制反馈。创建自定义异常涉及继承`Exception`类,如`CustomException`,并用它来抛出具有详细信息的错误。在实践中,可以为异常添加额外字段,如`DetailedException`的`errorCode`,以增强信息携带能力。使用自定义异常时,应明确目的、保持简洁、提供丰富信息并统一风格,使其成为高效错误处理的工具。
|
4天前
|
Java 程序员 开发者
【程序员必修课】那些年,我们踩过的Java坑:自定义异常,让你的代码不再“捉急”!
【6月更文挑战第19天】Java异常处理不仅是错误处理,更是程序健壮性的体现。自定义异常能提供更精确的错误信息,便于问题定位。通过继承`Exception`创建自定义异常类,如`NegativeValueException`,可使代码更优雅,降低维护难度。自定义异常还能携带额外信息,如错误代码,增强企业级应用的错误处理能力。善用自定义异常,提升代码质量和开发效率,是优秀编程实践的重要组成部分。
|
4天前
|
搜索推荐 Java 开发者
【实战指南】Java异常处理新高度:自定义异常,打造个性化的错误管理体系!
【6月更文挑战第19天】在Java中,自定义异常允许开发人员针对特定业务需求创建新的异常类型,增强代码可读性和维护性,特别是在大型项目中。它使错误处理更精确,避免通用异常的模糊性,提升程序稳定性。创建自定义异常需继承`Exception`或`RuntimeException`,提供有意义的构造函数,并注意序列化ID。使用时,通过`throw`抛出并在`try-catch`块中捕获。设计上,异常命名应明确,携带相关信息,避免过度使用,且保持一致性。自定义异常是构建健壮错误处理体系的关键。
|
1天前
|
Scala
scala 读取文件(中文)异常 thread "main" java.nio.charset.MalformedInputException: Input length = 1
scala 读取文件(中文)异常 thread "main" java.nio.charset.MalformedInputException: Input length = 1
4 0
|
1天前
|
Java
springboot 异常java.net.BindException: Address already in use: bind
springboot 异常java.net.BindException: Address already in use: bind
5 0
|
2天前
|
Java 程序员 编译器
杨校老师课堂之Java基础异常专题知识点整理
杨校老师课堂之Java基础异常专题知识点整理
4 0
|
4天前
|
IDE Java API
如何使用Java和Spring Boot来开发一个基本的RESTful API
如何使用Java和Spring Boot来开发一个基本的RESTful API
10 0