This week's book giveaway is in the OCPJP forum. We're giving away four copies of OCA/OCP Java SE 7 Programmer I & II Study Guide and have Kathy Sierra & Bert Bates on-line! See this thread for details.
Apperently with the MSSQL jdbc driver (and also the Data Direct Driver) you cannot close a connection twice. If you do so, something will get screwed in the driver. It wont show up all the time, just when you push the driver. So check your code and make sure you don't close a connection twice.
I spent alot of time going thru the microsoft and data direct web sites and couldn't find anything... It appears that I'm experiancing this, but am trying to confirm the bug.
According to the java api it's supposed to be a no-op -- The bug seems to be that it isn't a no-op.. The stack trace I'm getting when I try to close the connection is: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Object has been closed. at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source) at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source) at com.microsoft.jdbc.base.BaseConnection.validateClosedState(Unknown Source) at com.microsoft.jdbc.base.BaseStatement.validateClosedState(Unknown Source) at com.microsoft.jdbc.base.BasePreparedStatement.clearParameters(Unknown Source) at com.microsoft.jdbc.base.BasePreparedStatement.close(Unknown Source) at com.svtechnology.database.DBConnectionBitMechanic.destroy(DBConnectionBitMechanic.java:297)