#30 Proxool get stuck when shutting down pool

[Anonymous]

We have encountered following problem when testing our
application development framework OpenSubsystems with
Proxool.

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.acquire()
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.closeConnectionPool(PooledDatabaseConnectionFactoryImpl$ConnectionPoolDefinition)
line: 311
ProxoolDatabaseConnectionFactoryImpl(PooledDatabaseConnectionFactoryImpl).stop()
line: 529
ProxoolDatabaseConnectionFactoryTest$ProxoolDatabaseConnectionFactoryTestInternal(DatabaseConnectionFactoryBaseTest).tearDown()
line: 292
ProxoolDatabaseConnectionFactoryTest$ProxoolDatabaseConnectionFactoryTestInternal(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.

This problem can be also tracked in OpenSubsystems bug
database at
http://sourceforge.net/tracker/index.php?func=detail&aid=1491768&group_id=111437&atid=659213

[Bill Horsman]

Logged In: YES
user_id=91747

Thanks for the heads up. I'll take a look at this.

[roger5089]

Logged In: YES
user_id=1776553
Originator: NO

Dear all when i test this pool in tomcat with orcale database something occure the problem like this does someone know how to fix or modify the pool envirnments
roger5089@gmail.com
best regard
=========
007/10/1 下午 01:58:20 org.logicalcobwebs.proxool.ProxoolDriver connect嚴重的: Problem
org.logicalcobwebs.proxool.ProxoolException: Attempt to refer to a unregisteredpool by its alias 'myDB'
at org.logicalcobwebs.proxool.ConnectionPoolDefinition.doChange(ConnectionPoolDefinition.java:250)
at org.logicalcobwebs.proxool.ConnectionPoolDefinition.<init>(ConnectionPoolDefinition.java:147)
at org.logicalcobwebs.proxool.ProxoolFacade.registerConnectionPool(ProxoolFacade.java:96)
at org.logicalcobwebs.proxool.ProxoolDriver.connect(ProxoolDriver.java:77)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:193)
at org.apache.jsp.en.home.index_jsp._jspService(index_jsp.java:171)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:324)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:292)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:236)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)

[Bill Horsman]

Logged In: YES
user_id=91747
Originator: NO

roger5089: your bug isn't related to the original bug about problems shutting down. Can you create a new bug please, otherwise people (like me) are going to get confused. Thanks.