> Ok, so it's indeed broken. The thing is that there's no way to know if the > JDBC exception you get indicates that the connection is broken, that the SQL > is bad, or something else :-(
That's right. So the way i wrote the patch, i assume the connection is broken (and don't try to close it), create a new one, and try connection.prepareStatement again. If the connection was indeed broken, then with a bit of luck, we'll now have a valid one, and connection.prepareStatement won't throw an exception. If the SQL is bad or something else is the problem, well this time around, the exception thrown by connection.prepareStatement will get handled by the existing code. cheers, Jason -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
