DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33912>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33912 ------- Additional Comments From [EMAIL PROTECTED] 2005-05-06 13:09 ------- I've encountered the same deadlock and have a couple of additional comments: the bug is only when using PoolingDriver and a setting of minIdle > 0 in the GenericObjectPool configuration. Suggested interim workarounds: a) set minIdle = 0 in your configuration for the GenericObjectPool b) if you know you are connection pooling within the application code, retrieve a connection as follows: ObjectPool connectionPool = poolingDriver.getConnectionPool(name); Connection conn = (Connection)connectionPool.borrowObject(); This second method will allow you to have minIdle > 0 while avoiding the deadlock code path between threads. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]