Gaetano Mendola wrote:
> I had some OutOfMemory in the client side but not related with the
> Database interaction.
Are you sure there was no OutOfMemoryError thrown within the JDBC driver
code? (perhaps caused by some other part of the application exhausting
the heap?) The driver isn't very good about keeping connections in a
consistent state when unexpected exceptions are thrown. One possibility
is that OOME was thrown partway through reading or writing a message on
the protocol stream, but the driver did not invalidate that connection.
Subsequent use of the connection will then fail randomly since the
driver is out of sync with the message boundaries the server is expecting.
-O
