DruidDataSource配置如下

DruidDataSource dataSource = new DruidDataSource();
dataSource.setName("SqlServer");
dataSource.setDriverClassName(SqlUtil.getDriverClass(“${datasourcename}”));
dataSource.setMaxActive(200);
dataSource.setPoolPreparedStatements(false);
dataSource.setUrl("${url}");
dataSource.setUsername("${userName}");
dataSource.setPassword("${pwd}");
dataSource.setMaxWait(6000);
dataSource.setQueryTimeout(600);
dataSource.setMinIdle(20);
dataSource.setInitialSize(1);
dataSource.setTimeBetweenEvictionRunsMillis(60000);
dataSource.setMinEvictableIdleTimeMillis(300000);
dataSource.setValidationQuery("SELECT 1");
dataSource.setTestWhileIdle(false);
dataSource.setTestOnBorrow(false);
dataSource.setTestOnReturn(false);
dataSource.setDefaultReadOnly(true);
dataSource.setBreakAfterAcquireFailure(true);
return dataSource;

线上运行环境：
Server version: Apache Tomcat/8.0.30 OS Name: Linux JVM Version: 1.8.0_65-b17
JVM配置：
JAVA_OPTS=-Ddruid.registerToSysProperty=true -Duser.timezone=GMT+08 -server -Xms5g -Xmx5g -XX:MaxNewSize=1536m -XX:PermSize=128m -XX:MaxPermSize=512m -XX:+ExplicitGCInvokesConcurrent -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:-UseGCOverheadLimit -XX:+UseConcMarkSweepGC -XX:+PrintGCDateStamps -javaagent:/data/jvmMonitorAgent/jvmMonitorAgent-1.0.4-jdk7.jar="enable:true;config:/data/jvmMonitorAgent/jvmMonitorAgent.properties" -javaagent:/usr/local/apm_agent/apm.agent.bootstrap.jar -Dapm.applicationName=${DAOKEAPPUK} -Dapm.agentId=${DAOKEIP}-${DAOKEID} -Dapm.env=${DAOKEENVTYPE}
线上运行一段时间后会有大量的Druid-ConnectionPool-Create和Druid-ConnectionPool-Destroy线程，占比1:1，约共有9k个线程，大量的线程导致GC比较频繁最终运行的时间长会导致tomcat不响应。不知道是不是dataSource配置的姿势不对，系统会有几十个不同的数据库连接来满足不同人的需求。