Tomcat连接池满分析

最新推荐文章于 2021-11-29 11:52:30 发布

原创最新推荐文章于 2021-11-29 11:52:30 发布 · 置顶 · 2.2k 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#probe #线程满 #线程dump

java 专栏收录该内容

13 篇文章

订阅专栏

本文介绍了一种数据库连接池故障的排查方法，包括添加请求时间过滤器、使用日志进行Excel分析、通过JVisualVM进行线程Dump以及利用监控工具进行实时监控。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

"http-8080-455" - Thread t@684
   java.lang.Thread.State: WAITING
    at java.lang.Object.wait(Native Method)
    - waiting on <3934c6ec> (a org.apache.tomcat.dbcp.pool.impl.GenericObjectPool$Latch)

近期项目多次出现数据库连接不上的问题，初步确定是数据库连接数达到最大，但是按照实际情况计算是远远达不到最大数的，这就考虑到处理请求时间过长导致连接被占用，解决方案如下：

第一步：添加过滤器，抓取各个请求时间保存到日志

package junitParam;

import java.io.File;
import java.io.FileOutputStream;
import java.io.IOException;
import java.util.Date;

import javax.servlet.Filter;
import javax.servlet.FilterChain;
import javax.servlet.FilterConfig;
import javax.servlet.ServletException;
import javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;
import javax.servlet.http.HttpServletRequest;

import com.fto.m2.servlet.RequestAttributeKeys;
import com.fto.m2.servlet.RunData;
import com.inqgen.nursing.tools.DateUtils;

public class UsedTimeFilter implements Filter {

	public void init(FilterConfig filterConfig) throws ServletException {
		// TODO Auto-generated method stub

	}

	public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
		long t1 = System.currentTimeMillis();
		chain.doFilter(request, response);
		long t2 = System.currentTimeMillis();
		try {
			HttpServletRequest req = (HttpServletRequest) request;
			RunData rundata = (RunData) request.getAttribute(RequestAttributeKeys.RUNDATA);

			Date now = new Date();
			String time = DateUtils.format(now, "yyyyMMdd");
			File file = new File("c:\\usedtime");
			file.mkdir();
			FileOutputStream out = new FileOutputStream(new File("c:\\usedtime\\" + time), true);
			String s = "";
			if (rundata != null) {
				if (rundata.getMemberConnection() != null) {
					s += rundata.getMemberConnection().getSelf().getLogin();
				}
			}
			String ip = req.getHeader("X-Forwarded-For");
			if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) {
				ip = req.getHeader("Proxy-Client-IP");
			}
			if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) {
				ip = req.getHeader("WL-Proxy-Client-IP");
			}
			if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) {
				ip = req.getHeader("HTTP_CLIENT_IP");
			}
			if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) {
				ip = req.getHeader("HTTP_X_FORWARDED_FOR");
			}
			if (ip == null || ip.length() == 0 || "unknown".equalsIgnoreCase(ip)) {
				ip = req.getRemoteAddr();
			}

			out.write((DateUtils.format(new Date(), "yyyyMMdd HHmm") + "\tip:" + ip + "\t" + req.getRequestURI() + " usedtime:" + (t2 - t1) + "\t loginId" + s + "\r\n").getBytes());
			out.close();
		} catch (Exception e) {
			e.printStackTrace();
		}
	}

	public void destroy() {
		// TODO Auto-generated method stub

	}

}

第二步：把文本日志放到excel表格里面去除掉不需要的部分，根据耗时倒序排列，基本能发现调用次数最多且耗时较长的请求，我的表格长这个样子，事故发生时间是下午16:00左右，1550有大量的nursingmain/selectPatientData请求，这个时候可以结合thead hump分析