Chinaunix首页 | 论坛 | 博客
  • 博客访问: 1186832
  • 博文数量: 399
  • 博客积分: 8508
  • 博客等级: 中将
  • 技术积分: 5302
  • 用 户 组: 普通用户
  • 注册时间: 2009-10-14 09:28
个人简介

能力强的人善于解决问题,有智慧的人善于绕过问题。 区别很微妙,小心谨慎做后者。

文章分类

全部博文(399)

文章存档

2018年(3)

2017年(1)

2016年(1)

2015年(69)

2013年(14)

2012年(17)

2011年(12)

2010年(189)

2009年(93)

分类: 数据库开发技术

2018-04-12 20:08:34

作者说, HikariCP 是对死掉的connection防弹。

Generally speaking, HikariCP should be bulletproof with regards to broken connections.  In the case where the broken connection is detected by the com.zaxxer.hikari.proxy.ConnectionProxy there should absolutely be no way that that connection ever comes out of the pool again.

However, there is a possibility that the application (or framework in the stack) acquires a Connection, performs some action (which succeeds at commit()), but hangs onto the Connection rather than releasing it back quickly.  Subsequently, upon attempting to use the Connection, the application may find that it is dead.  In this case, HikariCP never got the connection back, and therefore could not detect that it was broken.  I have definitely seen Hibernate do this in the past -- based on configuration of its acquisition_mode or release_mode.

I suggest reading this issue to see if it helps, especially the last few comments.


Google forum:
!topic/hikari-cp/IpUjIJLA3H8
阅读(377) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~