Originally posted by Alin Sinpalean:
The connection is most likely closed by you (read "your pool implementation") calling close() on it.
Hi, Alin! I read it and there's no calling to
close() on my code or on the pool implementation.
Originally posted by Alin Sinpalean:
There's a very-very slight possibility that there's a communication error between the driver and SQL Server (either network or TDS protocol issue) and that's causing the connection to close, but I wouldn't bet on that.
I read something about the connection being closed by
SQL Server in a forum (or mail list, I don't remember). I'm positive that neither my code (or the pool) is closing the connections (I've searched for
close() calls all over it and in a bunch of different ways - with
ctrl + alt + h in
Eclipse, with search and with the "old-fashion" way: reading class after class).
Originally posted by Alin Sinpalean:
Try without the pool and if it works, then you know where the problem lies.
I've tried but I have other problems related. Creating and closing many connections (not using a pool) brings me performance issues and sometimes (after some time) I get a "Connection refused" (or something like that).
Don't know what else to do!
I'm struggling with the DBAs to read the logs from
SQL Server... Maybe these logs have a hint for me. Maybe.
[ November 10, 2005: Message edited by: MTulio Borges ]