Hello All,
I've noticed some odd behavior using Peers
in our Turbine application.
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.
However, use of the application results eventually
in an error from the driver, but only after
Tomcat is forced to reload classes (due to
their recompilation). I have not yet tried
to max out connections in different ways
within the app, so it may also break in
other ways.
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.
Has anyone else re-experienced this problem?
Am I missing the point that it wasn't fixed per
se to being with? I'm happy to look with a debugger
but I thought I'd ask first since: When it
comes to connection pooling, I'm about as ignorant
as a newbie (without the TDK) sending personal
email to Jon Stevens. :)
Thanks in advance,
Dave Kim
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
