项目部署在服务器上面的log ,memory leak,内存溢出,来大神帮忙解决
INFO: Pausing Coyote HTTP/1.1 on http-8080
Aug 11, 2014 1:00:02 AM org.apache.catalina.core.StandardService stop
INFO: Stopping service Catalina
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [/IGVault] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
Exception in thread "Timer-1" Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
Aug 11, 2014 1:00:04 AM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [/IGVault] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation.
org.hibernate.exception.GenericJDBCException: Cannot open connection
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:29)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:420)
at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:144)
at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:105)
at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1561)
at org.hibernate.loader.Loader.doQuery(Loader.java:661)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
at org.hibernate.loader.Loader.doList(Loader.java:2145)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2029)
at org.hibernate.loader.Loader.list(Loader.java:2024)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:375)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:308)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:153)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1106)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at com.igvault.dao.impl.AndroidApnsMessageDaoImpl.getDevicess(AndroidApnsMessageDaoImpl.java:25)
at com.igvault.service.MigrationListenner$1.run(MigrationListenner.java:39)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
Caused by: java.sql.SQLException: An SQLException was provoked by the following failure: java.lang.InterruptedException
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:65)
at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:62)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:531)
at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)
at org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:35)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:417)
... 17 more
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1315)
at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)
at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)
at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)
... 20 more
相关推荐
Slave memory leak and trigger oom-killer
"Slave memory leak and trigger oom-killer"问题描述:在MySQL数据库系统中,存在一个特定的问题,即从库(slave)出现内存泄漏并触发了内核的OOM
腾讯云CentOS7.5服务器上,手把手教你搞定Spring Boot项目从打包到上线的完整流程
本文详细介绍了在腾讯云CentOS7.5服务器上部署Spring Boot项目的完整流程,包括环境配置、项目打包、服务器部署及常见问题解决。特别针对腾讯云环境优化,提供从零开始的手把手教程,帮助开发者高效完成项目上线。
OpenClaw部署避坑指南:八大高频问题与实战解决方案
大语言模型(LLM)与工具链的集成是实现AI智能体自动化的核心技术原理,通过将模型能力与外部工具(如数据处理、浏览器操作等)连接,构建自动化工作流,从而在客服、数据分析、报告生成等应用场景中释放生产力。OpenClaw作为一个开源AI智能体框架,其核心价值在于提供了灵活可扩展的本地部署方案,允许开发者自由组合模型与技能。然而,在实际部署中,环境配置、容器网络、模型连接等工程实践环节常成为阻碍。本文聚焦于**Docker部署**与**Ollama模型配置**两大高频痛点,系统梳理从环境准备到生产维护的全链路避
Eclipse内存溢出
### Eclipse内存溢出问题解析与解决方案#### 一、内存溢出概述内存溢出(Memory Leak)是指程序运行过程中使用的内存超过系统所能提供的最大内存限制时所出现的问题。
内存泄露分析工具Memory_Analyzer_Tool(MAT)介绍.docx
MAT工具能够帮助开发者解决两个常见的内存泄露问题:永久保存区内存溢出和JVM调配使用的内存空间不足内存溢出。MAT工具可以快速查找解决系统崩溃、查看系统运行情况、提前找到系统内存使用上存在的问题。


Web 开发
