db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepa Remesh (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1692) Client driver does not use the query timeout value set using Statement.setQueryTimeout() for subsequent executions using the same statement object
Date Mon, 14 Aug 2006 23:40:14 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1692?page=all ]

Deepa Remesh updated DERBY-1692:
--------------------------------

    Attachment: TestQueryTimeout.java

Attaching a repro 'TestQueryTimeout.java'  based on jdbcapi/SetQueryTimeout test. Repro passes
with embedded driver but fails with client driver.

To run with embedded driver: run the command "java TestQueryTimeout" 
To run with client driver: Start network server and run "java TestQueryTimeout client"

As shown by the repro, client driver does not use the query timeout value set for a statement
for subsequent executions. This is the case for all the Statement.executeXXX methods. getQueryTimeout
returns the correct value. So I am guessing the problem is in network server not using the
query timeout set initially. As I am not sure where the problem is, I have put both Network
Client and server as the component.






> Client driver does not use the query timeout value set using Statement.setQueryTimeout()
for subsequent executions using the same statement object
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1692
>                 URL: http://issues.apache.org/jira/browse/DERBY-1692
>             Project: Derby
>          Issue Type: Bug
>          Components: Network Server, Network Client
>    Affects Versions: 10.2.0.0, 10.3.0.0
>            Reporter: Deepa Remesh
>         Attachments: TestQueryTimeout.java
>
>
> I will attach a repro with more details.

-- 
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

        

Mime
View raw message