Dirk,
I see your point about helping to detect poor logic, but wouldn't it be better to just
print out a warning log message stating that
the connection was double-closed, perhaps with a stack trace? That way, the code which
would be legal (according to the javadoc)
will still operate. This was
Hello all,
I just started using DBCP and am pretty happy with it, but I've come across something
that seems a bit strange to me. When a
connection received from the DBCP pool has close() called upon it two times, on the
second call, it will throw an SQL exception such
as:
java.sql.SQLException:
