Druid reports an error connection holder is null

 

 removeAbandonedTimeout = 180 （ namely 3 minute ）

adopt datasource.getConnontion() The connection obtained must be in removeAbandonedTimeout Called within the set time close(), Or this Connection It will automatically expire ( Namely conn Cannot exceed the specified lease term )

Because there are hundreds of thousands of data in circulation for saving and processing , So before the loop, we get Connection, This error will be reported after the loop is executed for a while , The solution is to increase the time , Or make your own judgment

summary :

    The connection pool is designed to prevent the program from forgetting to return the connection from the pool , Some parameters are provided to set a lease term , Using this can prevent connection leakage to some extent