We've spent some time today investigating what actually happens in the DataSource ... Not so easy since DBCP code is a little tricky !
We've observed that JDBC connections which are realeased from the pool by the Evictor are not physically closed : 1/ from the DataSource standpoint : the maximum size of the pool is never exceeded (numActive is always inferior to maxActive), 2/ but from the dataserver standpoint : the number of connections is always increasing (up to the maximum allowed by the server). We haven't identified the exact cause of this issue : for some unknown reason the DelegatingConnection.close() method consider the JDBC connection as already closed which is wrong. Next step tomorrow ... -- View this message in context: http://www.nabble.com/DataSource-configuration-for-production-tp17695975p17760106.html Sent from the OpenEJB User mailing list archive at Nabble.com.
