"Daniel L. Rall" wrote:
> [snip]
> > 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.
>
> So, I'm running multi-threaded here (as mentioned above), but I have
> more threads requesting connections--in their constructors, all created
> at once--than I have max number of connections in my pool. I'd rather
> not have to increase the maxium number of connections every time I need
> more threads (I assume that this would fix the problem).
FYI, setting the max number of connection to 12 or more (1 app + 11
threads) keeps the application from hanging (caught in a wait state).
This feels like a hack, however. I would love some input on addressing
this problem. Thanks guys. =)
> [snip]
--
Daniel Rall <[EMAIL PROTECTED]>
http://collab.net/ | open source | do the right thing
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
