commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34539] - [pool] Deadlock when evicting dbcp objects (testWhileIdle=true)
Date Fri, 10 Feb 2006 22:23:27 GMT
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=34539>.
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=34539


Sandy@McArthur.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         OS/Version|other                       |All
           Priority|P2                          |P3
           Platform|Other                       |All




------- Additional Comments From Sandy@McArthur.org  2006-02-10 23:23 -------
Looking at GenericKeyedObjectPool.Evictor and PoolingConnection I think this is
a problem with PoolingConnection because it is both a client for
GenericKeyedObjectPool and passes an instance of itself as the
KeyedPoolableObjectFactory for GenericKeyedObjectPool.

I'm not sure GenericKeyedObjectPool can be changed and remain thread safe to fix
this situation. I think PoolingConnection needs to be changed so it aquires
synchronization lock in the order of the GenericKeyedObjectPool instance first
and then itself.

Does an apache dev agree with me and want to punt this off to Dbcp?

-- 
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message