hikaricp - Log warning: Thread starvation or clock leap detected (housekeeper delta=springHikariConnectionPool) -

i'm using hikaricp 2.4.6 , @ tomcat 8 startup, warning message:

01-aug-2016 11:18:01.599 info [rmi tcp connection(4)-127.0.0.1] org.apache.catalina.core.applicationcontext.log initializing spring frameworkservlet 'spring mvc dispatcher servlet' [2016-08-01 11:18:01,654] artifact blueberry:war exploded: artifact deployed [2016-08-01 11:18:01,655] artifact blueberry:war exploded: deploy took 33,985 milliseconds aug 01 2016 11:26:52.802 [dev] (hikaripool.java:614) warn : com.zaxxer.hikari.pool.hikaripool - 9m13s102ms - thread starvation or clock leap detected (housekeeper delta=springhikariconnectionpool). 

i don't see other errors or issues reading/writing db. concerned about? tried searching around, no luck.

we're using hibernate 4.3.8.final on mysql 5 , mysql 5.1.39 connector spring 4.1.0.release. we're working upgrade hibernate 5 , see whether goes away, don't know whether matter.

i noticed there's newer version of hikaricp (2.4.7) resolved issue appearing on instance.

there's rundown of why clock leap detections might legitimately occur. quote external link brett woolridge:

this runs on housekeeper thread, executes every 30 seconds. if on mac os x, clocksource system.currenttimemillis(), other platform clocksource system.nanotime(). both in theory monotonically increasing, various things can affect such ntp servers. oses designed handle backward ntp time adjustments preserve illusion of forward flow of time.

this code saying, if time moves backwards (now < previous), or if time has "jumped forward" more 2 housekeeping periods (more 60 seconds), strange going on.

a couple of things might going on:

1. you running in virtual container (vmware, aws, etc.) reason doing particularly poor job of maintaining illusion of forward flow of time.

2. because other things occur in housekeeper thread -- specifically, closing idle connections -- possible reason closing connections blocking housekeeper thread more 2 housekeeping periods (60 seconds).

3. the server busy, cpus pegged, thread starvation occurring, preventing housekeeper thread running more 2 housekeeping periods.

considering these, maybe can provide additional context.

edit: note based on hikaricp 2.4.1 code. make sure running up-to-date version available.

(it looks parameters updated on warning statement in latest code.)