Here is an immature hypothesis for debugging this problem. It is based on abandoned connections.
Can someone please advise me where to find: * How does OO Base manage abandoned connections, which might occur upon code crashes before the connection.close() calls? * example test code and documentation for the OO Base Connection object management? * how to examine the current state of all OO Base active connections? * how to coerce the release of all connection objects currently checked out from OO (pooled and non-pooled)? * how to change or reset management parameters (maxActive, expire-idle-time, etc.) of OO Base connections (pooled and non-pooled)? Thanks. Ray ----- references: www.mail-archive.com/[email protected]/msg00028.html HSQLDB JDBC connection pool lockup javax.sql.PooledConnection javax.sql.ConnectionPoolDataSource Most database softwares have an inherent limit on the number of active database connection sessions. Some softwares allow users some control in managing the active database connections. I recalled that I turned on and off the OO connection pooling for a number of database drivers, including HSQLDB, during my past OO BeanShell trials. I read about Java PooledConnection in the references. I have not found anything about OO PooledConnection Manager. It was pointed out in the reference below that the connection pool can be depleted if the pool manager does not properly handle abandoned connections, which might occur upon code crash before the connection.close() calls. Then the getConnection() call will always fail due to the depletion of connection resources. OO Base connection requests will deadlock if OO does not expire abandoned connections after a preset idle time. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
