Hi Casey, The important thing to understand here is that jOOQ doesn't pool any of your connections. It externalises this responsibility through the ConnectionProvider SPI. Either, you have implemented your own ConnectionProvider, or you have implicitly chosen one of the two defaults:
- DefaultConnectionProvider (e.g. when you call DSL.using(connection)) - DataSourceConnectionProvider (e.g. when you call DSL.using(datasource)) In the first case, jOOQ will never call Connection.close() as that will be your responsibility. In the second case, jOOQ will always call Connection.close() as the general DataSource contract is that connections have to be closed after usage for the DataSource to implement whatever connection pool semantics. I suspect your problem lies in the configuration of your connection pool / data source. Hope this helps, Lukas 2018-03-21 19:37 GMT+01:00 Casey Merrill <[email protected]>: > I'm aware that checkConnectionOnBorrow and upping the validation interval > to something shorter than the default 30 seconds will reduce the errors > but I'd like to drop the connection on the first failure. > > -- > You received this message because you are subscribed to the Google Groups > "jOOQ User Group" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
