> David K. Kim wrote
> We are using the development version of the
> iSPRINTA JDBC driver, which limits DB connections
> to 2. I've specified such in our TR.props file,
> and a casual inspection of the source and logs
> suggests that it is being correctly read in
> (rather than defaulting). So the connection pool
> *should* know how many connections it can make.
>
I'm using the same, and Turbine is certainly getting
the values OK. I can force the ConnectionPool to
time out, but I never get the iSPRINTA exception.
>
> I'm guessing that this is due to DB connections
> floating around pending garbage collection,
> which has been mentioned here and possibly
> fixed (?) by Paul O'Leary and Daniel Rall.
>
I'm sorry, but I have totally missed talk about pending
garbage collection. I submitted a patch so that when
DBConnection is garbage collected, it returns the
underlying Connection to the pool. Allowing this to
happen is not neat programming though, and caused the
Connection to leak completely in the old code.
I just checked out the ConnectionPool code and
it does not seem to me that there are any other gc
dependent issues. I am not an expert in class
reloading, so I can't rule out some freaky stuff
in connection with that.
Magnus Torfason
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
