Spring HikariDataSource Hikari資料庫連線池監控 總連線數/活躍連線數/空閒連線數/阻塞在獲取連線的執行緒數
阿新 • • 發佈:2021-01-29
技術標籤:spring
文章目錄
private HikariPoolMXBean proxy;
private boolean hasStarted;
@Resource
private HikariDataSource hikariDataSource;
@Resource
private GenericRebateRequestManager manager;
@Scheduled(cron = "0/1 * * * * *")
public void monitor() {
try {
if (null == proxy) {
MBeanServer mBeanServer = ManagementFactory.getPlatformMBeanServer();
ObjectName poolName = new ObjectName("com.zaxxer.hikari:type=Pool (" + hikariDataSource.getPoolName() + ")");
proxy = JMX.newMXBeanProxy(mBeanServer, poolName, HikariPoolMXBean.class);
} else {
log.info("{}, {}, {}, {}" , proxy.getTotalConnections(), proxy.getActiveConnections(), proxy.getIdleConnections(), proxy.getThreadsAwaitingConnection());
}
} catch (Throwable cause) {
log.error("", cause);
}
}
@Scheduled(cron = "0/1 * * * * *")
public void useDatabaseConnectionPool() {
if (!hasStarted) {
hasStarted = true;
ExecutorService executor = Executors.newFixedThreadPool(100);
for (int i = 0; i < 49; i++) {
executor.submit((Runnable) () -> {
while (true) {
try {
manager.queryByRequestNo("20201229174110092320400126954225");
} catch (Throwable cause) {
log.info(ExceptionUtils.getRootCauseMessage(cause));
}
}
});
}
}
}
注意
- 監控值(空閒連線數 ,活動連線,總連線數,等待連線的執行緒數)是非常短暫的。由於每個統計資料都是時間敏感的,並且是獨立收集的,所以在短時間內可能無法“累計”。不要基於這些值進行任何程式設計決策,它們僅用於監視。
- 配置
spring.datasource.hikari.register-mbeans=true
- 必須得至少獲取一個連線, 不然會一直報錯, 在這裡我啟動了另一個定時任務執行查詢操作
java.lang.reflect.UndeclaredThrowableException: null at com.sun.proxy.$Proxy174.getTotalConnections(Unknown Source) ~[?:?] at com.bestpay.redbag.web.controller.MrathenaController.datasource(MrathenaController.java:38) ~[classes/:?] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_202] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_202] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_202] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_202] at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84) ~[spring-context-5.2.7.RELEASE.jar:5.2.7.RELEASE] at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-5.2.7.RELEASE.jar:5.2.7.RELEASE] at org.springframework.scheduling.concurrent.ReschedulingRunnable.run(ReschedulingRunnable.java:93) ~[spring-context-5.2.7.RELEASE.jar:5.2.7.RELEASE] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_202] at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_202] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_202] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) ~[?:1.8.0_202] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_202] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_202] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_202] Caused by: javax.management.InstanceNotFoundException: com.zaxxer.hikari:type=Pool (hikari) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095) ~[?:1.8.0_202] at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:643) ~[?:1.8.0_202] at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678) ~[?:1.8.0_202] at com.sun.jmx.mbeanserver.MXBeanProxy$GetHandler.invoke(MXBeanProxy.java:122) ~[?:1.8.0_202] at com.sun.jmx.mbeanserver.MXBeanProxy.invoke(MXBeanProxy.java:167) ~[?:1.8.0_202] at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:258) ~[?:1.8.0_202] ... 16 more
可配調整 spring.datasource.hikari.maximum-pool-size=50
, spring.datasource.hikari.minimum-idle=50
, spring.datasource.hikari.connection-timeout=250
等配置來測試效果