borrow
tomcat-jdbc-8.5.11-sources.jar!/org/apache/tomcat/jdbc/pool/ConnectionPool.java
/** * Validates and configures a previously idle connection * @param now - timestamp * @param con - the connection to validate and configure * @param username The user name to use for the connection * @param password The password for the connection * @return a connection * @throws SQLException if a validation error happens */ protected PooledConnection borrowConnection(long now, PooledConnection con, String username, String password) throws SQLException { //we have a connection, lets set it up //flag to see if we need to nullify boolean setToNull = false; try { con.lock(); if (con.isReleased()) { return null; } //evaluate username/password change as well as max age functionality boolean forceReconnect = con.shouldForceReconnect(username, password) || con.isMaxAgeExpired(); if (!con.isDiscarded() && !con.isInitialized()) { //here it states that the connection not discarded, but the connection is null //don"t attempt a connect here. It will be done during the reconnect. forceReconnect = true; } if (!forceReconnect) { if ((!con.isDiscarded()) && con.validate(PooledConnection.VALIDATE_BORROW)) { //set the timestamp con.setTimestamp(now); if (getPoolProperties().isLogAbandoned()) { //set the stack trace for this pool con.setStackTrace(getThreadDump()); } if (!busy.offer(con)) { log.debug("Connection doesn"t fit into busy array, connection will not be traceable."); } return con; } } //if we reached here, that means the connection //is either has another principal, is discarded or validation failed. //we will make one more attempt //in order to guarantee that the thread that just acquired //the connection shouldn"t have to poll again. try { con.reconnect(); reconnectedCount.incrementAndGet(); int validationMode = getPoolProperties().isTestOnConnect() || getPoolProperties().getInitSQL()!=null ? PooledConnection.VALIDATE_INIT : PooledConnection.VALIDATE_BORROW; if (con.validate(validationMode)) { //set the timestamp con.setTimestamp(now); if (getPoolProperties().isLogAbandoned()) { //set the stack trace for this pool con.setStackTrace(getThreadDump()); } if (!busy.offer(con)) { log.debug("Connection doesn"t fit into busy array, connection will not be traceable."); } return con; } else { //validation failed. throw new SQLException("Failed to validate a newly established connection."); } } catch (Exception x) { release(con); setToNull = true; if (x instanceof SQLException) { throw (SQLException)x; } else { SQLException ex = new SQLException(x.getMessage()); ex.initCause(x); throw ex; } } } finally { con.unlock(); if (setToNull) { con = null; } } }return
tomcat-jdbc-8.5.11-sources.jar!/org/apache/tomcat/jdbc/pool/ConnectionPool.java
/** * Returns a connection to the pool * If the pool is closed, the connection will be released * If the connection is not part of the busy queue, it will be released. * If {@link PoolProperties#testOnReturn} is set to true it will be validated * @param con PooledConnection to be returned to the pool */ protected void returnConnection(PooledConnection con) { if (isClosed()) { //if the connection pool is closed //close the connection instead of returning it release(con); return; } //end if if (con != null) { try { returnedCount.incrementAndGet(); con.lock(); if (con.isSuspect()) { if (poolProperties.isLogAbandoned() && log.isInfoEnabled()) { log.info("Connection(" + con + ") that has been marked suspect was returned." + " The processing time is " + (System.currentTimeMillis()-con.getTimestamp()) + " ms."); } if (jmxPool!=null) { jmxPool.notify(org.apache.tomcat.jdbc.pool.jmx.ConnectionPool.SUSPECT_RETURNED_NOTIFICATION, "Connection(" + con + ") that has been marked suspect was returned."); } } if (busy.remove(con)) { if (!shouldClose(con,PooledConnection.VALIDATE_RETURN)) { con.setStackTrace(null); con.setTimestamp(System.currentTimeMillis()); if (((idle.size()>=poolProperties.getMaxIdle()) && !poolProperties.isPoolSweeperEnabled()) || (!idle.offer(con))) { if (log.isDebugEnabled()) { log.debug("Connection ["+con+"] will be closed and not returned to the pool, idle["+idle.size()+"]>=maxIdle["+poolProperties.getMaxIdle()+"] idle.offer failed."); } release(con); } } else { if (log.isDebugEnabled()) { log.debug("Connection ["+con+"] will be closed and not returned to the pool."); } release(con); } //end if } else { if (log.isDebugEnabled()) { log.debug("Connection ["+con+"] will be closed and not returned to the pool, busy.remove failed."); } release(con); } } finally { con.unlock(); } } //end if } //checkInvalidation
/**
* Returns true
if the connection pool is configured
* to do validation for a certain action.
* @param action The validation action
*/
private boolean doValidate(int action) {
if (action == PooledConnection.VALIDATE_BORROW &&
poolProperties.isTestOnBorrow())
return true;
else if (action == PooledConnection.VALIDATE_RETURN &&
poolProperties.isTestOnReturn())
return true;
else if (action == PooledConnection.VALIDATE_IDLE &&
poolProperties.isTestWhileIdle())
return true;
else if (action == PooledConnection.VALIDATE_INIT &&
poolProperties.isTestOnConnect())
return true;
else if (action == PooledConnection.VALIDATE_INIT &&
poolProperties.getInitSQL()!=null)
return true;
else
return false;
}
想获取最新内容,请关注微信公众号
文章版权归作者所有,未经允许请勿转载,若此文章存在违规行为,您可以联系管理员删除。
转载请注明本文地址:https://www.ucloud.cn/yun/35494.html
摘要:序提供了可以用来监控的执行情况,默认提供了好几个现成的可以用,以及就是其中的两个。这个定义了一些抽象方法供子类实现。主要实现了方法这里同样适用了的动态代理,包装了这里记录了的执行耗时,然后跟阈值对比,判断是否记录到 序 tomcat提供了JdbcInterceptor可以用来监控jdbc的执行情况,默认提供了好几个现成的interceptor可以用,SlowQueryReport以及S...
摘要:开启参数或者连接池配置想获取最新内容,请关注微信公众号 开启PoolSweeper tomcat-jdbc-8.5.11-sources.jar!/org/apache/tomcat/jdbc/pool/PoolProperties.java @Override public boolean isPoolSweeperEnabled() { boolean ti...
摘要:本章主要是贴出一些相关的配置参数,如果需要修改添加对应的参数配置即可。 本章主要是贴出一些SpringBoot相关的配置参数,如果需要修改添加对应的参数配置即可。 application.properties # ---------------------------------------- # CORE PROPERTIES # --------------------------...
摘要:连接池的名称指定由连接池所创建的连接的自动提交状态。由连接池所创建的连接对数据库的只读属性指定由连接池所创建的连接的事务级别。以毫秒表示的当连接池中没有可用连接时等待可用连接返回的时间,超时则抛出异常,值为时无限期等待。 什么是连接池 什么是 Connection Pool -- 连接池呢? 我就不解释了。不太清楚的看这篇文章 [生产级别Nodejs开发实践-使用连接池](这篇文章...
摘要:连接池的名称指定由连接池所创建的连接的自动提交状态。由连接池所创建的连接对数据库的只读属性指定由连接池所创建的连接的事务级别。以毫秒表示的当连接池中没有可用连接时等待可用连接返回的时间,超时则抛出异常,值为时无限期等待。 什么是连接池 什么是 Connection Pool -- 连接池呢? 我就不解释了。不太清楚的看这篇文章 [生产级别Nodejs开发实践-使用连接池](这篇文章...
阅读 3303·2023-04-25 18:52
阅读 2305·2021-11-22 15:31
阅读 3412·2021-11-16 11:44
阅读 2788·2021-11-11 16:54
阅读 1094·2021-10-22 09:54
阅读 1635·2021-10-08 10:05
阅读 2850·2021-09-29 09:42
阅读 413·2021-09-26 09:55