Phil Steitz wrote on 13. Feb 2024 20:46 (GMT +01:00): > Thanks, Gary. I agree with everything below. I think it's best to just > leave things as they are.
If it’s plugable the project might not have to care, But then how to fix the reported problem? Do we have an idea what’s causing it? And a extension to that, using a conn3crion pool you expect it abstracts and handles all Those idiosyncrasies of different drivers, platforms and JDBC interpretations. Just giving Up is not the best option. In my experience with a properitary (but very robust pool since it handles a small number of drivers) throwing away connections on concrete suspicion turned out to be helpful. Either by configurable state, substrings of error messages or actual sqlexception subtypes. But maybe additional validation is also fine as long as it uses strict timeouts, some control for paralysis and starvation. If I understand this would happen in the mentioned problem case, so is there a timeout missing. Having said that as a tip to OP use tcpkeepalive and lower the timeouts. It saved my ass more than once, especially with VIPs in place. Gruss Bernd — https://bernd.eckenfels.net --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
