Re: [DBCP] test failure in TestPStmtPoolingBasicDataSource.testMultipleThreads1()

2014-04-13 Thread Phil Steitz
On 4/13/14, 4:21 PM, sebb wrote: > I added some debug to DelegatingStatement and it appears that > isClosed() is sometimes being called from a different thread than the > one used to create the instance. > > I'm not sure why this should be, because the statements are created in > the TestConnection

Re: [DBCP] test failure in TestPStmtPoolingBasicDataSource.testMultipleThreads1()

2014-04-13 Thread Phil Steitz
See comments in DBCP-415. I think the problem is the finalizer. > On Apr 13, 2014, at 4:21 PM, sebb wrote: > > I added some debug to DelegatingStatement and it appears that > isClosed() is sometimes being called from a different thread than the > one used to create the instance. > > I'm not su

[DBCP] test failure in TestPStmtPoolingBasicDataSource.testMultipleThreads1()

2014-04-13 Thread sebb
I added some debug to DelegatingStatement and it appears that isClosed() is sometimes being called from a different thread than the one used to create the instance. I'm not sure why this should be, because the statements are created in the TestConnectionPool.PoolTest.run() method and as far as I k