Hi, i noticed that ConnectionSapDB.isClosed() sends a small request to the Server to test, if the connection is still alive. I also remembered that the JDBC-driver automatically reconnects, if the connection is broken.
A small test revealed, that also the isClosed()-method causes a reconnect. I think, that this is not a good idea. ConnectionsPools use isClosed() to determine if a connection is still valid. If not, the connection is kicked out of the pool and a new one is created if needed. So the test, if the connection is closed or not, is pretty useless right now, since in normal operation it will cause a reconnect and return false. I would prefer, that isClosed() does not cause a reconnect. AFAIK, isClosed() is not even supposed to really test the connection. It's a great feature, that MaxDB's JDBC-driver sends a small packet to test the connection, but it currently causes a reconnect. Thanks Sven -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
