db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olav Sandstaa (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1090) Implement Connection.isValid as defined by JDBC4
Date Fri, 12 May 2006 11:19:09 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1090?page=all ]

Olav Sandstaa updated DERBY-1090:

    Attachment: brokeredlogical1090.diff

This patch (brokeredlogical1090.diff) implemets support for Connection.isValid for pooled
and XA connections. 

Testing of isValid for pooled and XA connections is implemented in the jdbc4/ConnectionTest.junit.
This test is currently not part of either the jdbc4 suite or derbyall. 

svn status reports:

M      java/engine/org/apache/derby/iapi/jdbc/BrokeredConnection40.java
M      java/testing/org/apache/derbyTesting/functionTests/tests/jdbc4/ConnectionTest.java
M      java/client/org/apache/derby/client/am/LogicalConnection40.java

I have run the jdbc4/ConnectionTest.junig, the JDBC4 test suite and derbyall with the patch.
Only failure was in tools/derbyrunjartest.java. 

The patch can be reviewed and committed.

> 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:
>  Attachments: brokeredlogical1090.diff, client1090_patch1.diff, client1090_patch2.diff,
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
> 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:
For more information on JIRA, see:

View raw message