Hi Daniel,
What do you mean by 'standalone' mode? I assume that you have pulled the
connection pool code out and are running it in a different application ... ?
Let me make this point related to the wait() in getPooledConnection: this
wait relies on a connection being released in order to wake up. That is,
the notify() that will wake up threads from this wait() is in
releaseConnection. Now here's the important question about 'standalone'
mode: how many threads are there? If you're using the connection pool in an
application that only has one thread (i.e. a regular old app) you are SOL
when you hit that wait() because there are no other threads in the app that
can come wake up the main thread.
This is why I need to understand what you mean by 'standalone'. Hope I'm
making sense.
cheers,
PaulO.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Daniel L. Rall
Sent: Wednesday, September 13, 2000 10:50 PM
To: Turbine
Subject: standalone connection pool bug?
Importance: High
[snip]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
