[ http://issues.apache.org/jira/browse/DERBY-1692?page=comments#action_12428205 ] Knut Anders Hatlen commented on DERBY-1692: -------------------------------------------
I think this happens because the client only sends the timeout value when it has changed. For PreparedStatement and CallableStatement this is OK since there is a one-to-one correspondence between these kinds of statements on the client and on the server. For a Statement object on the client, a new PreparedStatement is created on the server each time one of the execute methods is called. Therefore, the timeout value should be sent each time a Statement is executed. > 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 Client, Network Server > 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
