gpt4 book ai didi

java - Tomcat连接池废弃问题

转载 作者:行者123 更新时间:2023-11-28 22:39:42 24 4
gpt4 key购买 nike

我正在努力解决 Tomcat 连接池错误。在运行生成字符串值的简单存储过程后,在运行时会抛出以下错误。

WARNING: Connection has been abandoned PooledConnection[ConnectionID:45 ClientConnectionId: 7817280c-3f7e-4239-a009-3aedd0a855e8]:java.lang.Exception
at org.apache.tomcat.jdbc.pool.ConnectionPool.getThreadDump(ConnectionPool.java:1096)
at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:799)
at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:648)
at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnection(ConnectionPool.java:200)
at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnection(DataSourceProxy.java:128)
at util.ThreadLocalUtil.getConnection(ThreadLocalUtil.java:55)
at webapp.dao.WebApplicationDAO.getConnection(WebApplicationDAO.java:30)
at webapp.dao.AccountDAO.generateAccountId(AccountDAO.java:827)
at webapp.bo.Account.generateUserAccountId(Account.java:285)
at webapp.actions.AddUserAccountUNZAction.execute(AddUserAccountUNZAction.java:79)
at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)
at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)
at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)

我对该错误的了解是连接已打开但未关闭。在帐户 dao 中运行存储过程时打开连接。下面是调用存储过程的代码块。

Connection conn = null;
CallableStatement stmt = null;
ResultSet rs = null;
try {

conn = getConnection();
stmt = conn.prepareCall(sqlWebAppGenerateUserId);
stmt.setString(1, base);
rs = stmt.executeQuery();
String res = null;
if (rs.next()) {
res = rs.getString(1);
}

if (res == null) {
throw new RuntimeException("Failed to generate user id.");
}

return res;
} catch (SQLException e) {
LOG.error("{}", e);
throw new RuntimeException(e);
}finally {
if (stmt != null) {
try {
stmt.close();
} catch (SQLException e) {
LOG.error(e.getMessage(), e);
}
}
if (rs != null) {
try {
rs.close();
conn.close();
} catch (SQLException e) {
LOG.error(e.getMessage(), e);
}
}

}

如您所见,我正在使用 finally block 来关闭连接等。

我无法解释仍然抛出错误的原因以及如何调试和解决此问题。任何帮助将不胜感激

最佳答案

仅当 rs != null 时才关闭 conn,这意味着每次查询失败时连接都不会关闭。

我还建议切换到 try-with-resources而不是编写可能导致错误的笨拙的 finally block 。

关于java - Tomcat连接池废弃问题,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/47435740/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com