On Nov 20, 2007 11:15 PM, Phil Steitz <[EMAIL PROTECTED]> wrote: > After running some tests and looking carefully again at the stack > traces above, I think that while removing the listener on destroy per > DBCP-216 is a good idea and will resolve this problem, the reason that > it has not been reported up to now is most likely that (assuming I am > understanding the stack traces correctly - unfortunately I can find no > documentation for the Sybase classes) the driver is indirectly > generating a questionable connectionClosed event when the > SybPooledConnection closes the SybConnectionProxy. See > http://bugs.mysql.com/bug.php?id=884 for an argument for why this is > questionable. IIUC, your second stack trace (triggered by > destroyObject) matches the bug repoorted there. > > In any case, we should clean up listeners better in DBCP. I will do > that. Thanks again for reporting this. >
Done in r598045. I deployed a new snapshot to the apache snapshots repository (http://people.apache.org/repo/m2-snapshot-repository/commons-dbcp/commons-dbcp/) It would be great if you could verify that this resolves the Sybase problem. Phil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
