Re: Tomcat DBCP 8.0.18 issue

2015-06-03 Thread Tweak Ronaldo
Hmm, interesting... Thanks for explanation Mark! 2015-06-03 12:22 GMT+03:00 Mark Thomas ma...@apache.org: On 03/06/2015 07:24, Tweak Ronaldo wrote: Thanks Mark, yes I have mixed together Tomcat JDBC 8 and DBCP 7, my bad. Although I don't understand why Tomcat JDBC don't use DBCP as default

Re: Tomcat DBCP 8.0.18 issue

2015-06-03 Thread Mark Thomas
On 03/06/2015 07:24, Tweak Ronaldo wrote: Thanks Mark, yes I have mixed together Tomcat JDBC 8 and DBCP 7, my bad. Although I don't understand why Tomcat JDBC don't use DBCP as default solution for connections pooling. Tomcat does - and always has - used Commons DBCP for connection pooling by

Re: Tomcat DBCP 8.0.18 issue

2015-06-03 Thread Tweak Ronaldo
Thanks Mark, yes I have mixed together Tomcat JDBC 8 and DBCP 7, my bad. Although I don't understand why Tomcat JDBC don't use DBCP as default solution for connections pooling. 2015-06-02 16:59 GMT+03:00 Mark Thomas ma...@apache.org: On 01/06/2015 14:22, Tweak Ronaldo wrote: Hello guys,

Re: Tomcat DBCP 8.0.18 issue

2015-06-03 Thread Антон Мацюк
Mark, big thanks for a quick historical review, it was very intreresting! I was thinking that tomcat-jdbc is something new, but wasn't sure about project maintenance. 2015-06-03 12:22 GMT+03:00 Mark Thomas ma...@apache.org: On 03/06/2015 07:24, Tweak Ronaldo wrote: Thanks Mark, yes I have

Re: Tomcat DBCP 8.0.18 issue

2015-06-02 Thread Konstantin Kolinko
2015-06-01 16:22 GMT+03:00 Tweak Ronaldo twea...@gmail.com: Hello guys, we have migrated to Tomcat DBCP 8.0.18 from 7.0.37 recently and faced the following issue: after database restart (Postgres), our application wasn't been able to restore connectivity to DB, all connections were closed and

Re: Tomcat DBCP 8.0.18 issue

2015-06-02 Thread Mark Thomas
On 01/06/2015 14:22, Tweak Ronaldo wrote: Hello guys, Assuming you don't want to limit your question to men only, you would be better to use of of the following greetings: Hello, Hello all, Hello folks, etc. we have migrated to Tomcat DBCP 8.0.18 from 7.0.37 recently and faced the following