DBCP2 to HikariCP worked o.k. till DB became unavailable

365 views

Skip to first unread message

Haris Hodzic

unread,

Jun 14, 2016, 6:08:35 PM6/14/16

to HikariCP

Hi there,

This is my first post and we recently were looking into moving from DBCP2 to HikariCP since DBCP2 seems to have issues with reusing pool connections.

We decided to run Hikari on one server and other 14 running with DBCP2. We have a nightly maintenance on the DB we connect to and during this maintenance we experience high we response time. Once the DB recovers DBCP2 servers go back down to normal operation where Hikari server shoots up to about 4-5 seconds web response time. Normal is around 100 ms.

Hikari seems promising but we're not sure what might have occurred here. If anybody can give us some pointers as to what we might wanna adjust we'd greatly appreciate it. Also during the outage we noticed large number of 302 httpResponseCodes. About 30K in 3 hours. DBCP2 servers did not record any of these.
Thank you.
Haris

Brett Wooldridge

unread,

Jul 6, 2016, 9:48:10 AM7/6/16

to HikariCP

What version of HikariCP are you running? Can you post the configuration that you are using? I would suggest enabling DEBUG level logging, HikariCP is not too noisy, as doing so might reveal the source of the issue.