Hi,
We've just had an interesting moment or two tracking down some very
strange JDBC connection problems, which turn out to be caused by a piece
of our code returning a JDBC connection to a DBCP pool more than once.
The reference to the PoolableConnection makes it onto the list twice,
and from then on multiple users can be allocated the same connection at
the same time in the future, and cause interference by closing each
other out, or emptying result sets....
My question here is whether protection against this should be provided
by DBCP (kinda opposite to the abandoned connection functionality) or
POOL (more like a set of objects than a list)?
Any thoughts?
Mike
--
To unsubscribe, e-mail: <mailto:commons-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-user-help@;jakarta.apache.org>
