[ http://issues.apache.org/jira/browse/DERBY-1090?page=comments#action_12371853 ]
Rick Hillegas commented on DERBY-1090: -------------------------------------- Looks good to me. The jdbc4 tests run cleanly. Derbyall only has errors which I see in a clean client: wisconsin, sysinfo, sysinfo_withproperties, xaSimplePositive, and a new failure in SURTest caused by: > java.lang.NoSuchMethodError: main > Exception in thread "main" Test Failed. I have committed embedded1090_isClosed.diff at subversion revision 388771. > Implement Connection.isValid as defined by JDBC4 > ------------------------------------------------ > > Key: DERBY-1090 > URL: http://issues.apache.org/jira/browse/DERBY-1090 > Project: Derby > Type: Sub-task > Components: JDBC > Reporter: Olav Sandstaa > Assignee: Olav Sandstaa > Priority: Minor > Fix For: 10.2.0.0 > Attachments: embedded1090-isclosed.diff, embedded1090-query.diff > > The Javadoc for JDBC4 says this about Connection.isValid: > boolean isValid(int timeout) throws SQLException > Returns true if the connection has not been closed and is still valid. The > driver shall submit a query on the connection or use some other mechanism > that positively verifies the connection is still valid when this method is > called. > The query submitted by the driver to validate the connection shall be > executed in the context of the current transaction. > Parameters: timeout - - The time in seconds to wait for the database > operation used to validate the connection to complete. If the timeout period > expires before the operation completes, this method returns false. A value of > 0 indicates a timeout is not applied to the database operation. > Returns: true if the connection is valid, false otherwise -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
