This content has been marked as final. Show 1 reply
Inactive timeouts should occur only if your code has not used the JDBC connection (or one of it's subobjects) for that long. Even if your code is simply waiting for a query to return results from the DBMS, or for a ResultSet to respond, that is considered active. It should be only for truly inactive JDBC connections that your timeout will trigger. It is only you who can know if your code has long periods of non-JDBC processing while you're still holding on to (and perhaps needing) a JDBC connection.
Edited by: Joe Weinstein on Jan 21, 2013 9:16 AM