Menu

#287 Proxool get stuck when shutting down pool

CVS_Head
open
nobody
Core (45)
5
2013-02-20
2006-05-19
Miro Halas
No

When executing CoreTests test case after deploying
core-app.war using WebLogic 9.1 connected to MS SQL
Server 2005 SP 1 using jTDS 1.2 the test hung. THe
stack trace from the debugger was

Thread [[STUCK] ExecuteThread: '0' for
queue: 'weblogic.kernel.Default (self-tuning)']
(Suspended)
Object.wait(long) line: not available [native
method]
WriterPreferenceReadWriteLock$WriterLock
(Object).wait() line: 474 [local variables
unavailable]
WriterPreferenceReadWriteLock$WriterLock.acqui
re() line: 254
ConnectionPool.acquirePrimaryWriteLock()
line: 1002
ConnectionPool.shutdown(int, String) line: 476
ProxoolFacade.removeConnectionPool(String,
ConnectionPool, int) line: 170
ProxoolFacade.removeConnectionPool(String,
int) line: 185
ProxoolFacade.removeConnectionPool(String)
line: 251
ProxoolDatabaseConnectionFactoryImpl.closeConn
ectionPool
(PooledDatabaseConnectionFactoryImpl$ConnectionPoolDef
inition) line: 311
ProxoolDatabaseConnectionFactoryImpl
(PooledDatabaseConnectionFactoryImpl).stop() line: 529
ProxoolDatabaseConnectionFactoryTest$ProxoolDa
tabaseConnectionFactoryTestInternal
(DatabaseConnectionFactoryBaseTest).tearDown() line:
292
ProxoolDatabaseConnectionFactoryTest$ProxoolDa
tabaseConnectionFactoryTestInternal(TestCase).runBare
() line: 136
TestResult$1.protect() line: 106
TestResult.runProtected(Test, Protectable)
line: 124
TestResult.run(TestCase) line: 109

It seems like Proxool got stuck waiting indefinitly
on a lock.

Discussion

  • Miro Halas

    Miro Halas - 2006-05-19

    Logged In: YES
    user_id=166079

    The Proxool version used was 0.9.0RC2.
    This problem can be tracked in Proxool bug database at
    http://sourceforge.net/tracker/index.php?
    func=detail&aid=1491771&group_id=53958&atid=472195

     
  • Miro Halas

    Miro Halas - 2006-05-19

    Logged In: YES
    user_id=166079

    This cannot be consistently reproduced. Several times it
    run just fine.

     

Log in to post a comment.