[
https://issues.apache.org/jira/browse/DERBY-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-2029:
--------------------------------------
Issue & fix info: [Repro attached]
Triaged for 10.5.2.
> Query timeout does not take effect if server machine crashes
> ------------------------------------------------------------
>
> Key: DERBY-2029
> URL: https://issues.apache.org/jira/browse/DERBY-2029
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Network Client
> Affects Versions: 10.2.2.0, 10.3.1.4
> Environment: Solaris 10, JDK 1.5
> Reporter: Olav Sandstaa
> Priority: Minor
> Attachments: QueryTimeout.java
>
>
> An application using the client driver will hang "infinite" if the
> server machine running the Derby server crashes during execution of a
> query even if it has specified a query timeout using
> Statement.setQueryTimeout().
> This problem can be reproduced (at least on Solaris 10) by:
> 1. starting a Derby server on one machine and a Derby client on the second
> machine.
> 2. In a Java program, create a connection and a statement and set the
> query timeout for the statement to a few seconds by:
> Statement.setQueryTimeout(10)
> 3. Execute a query that take some time (more than 10 seconds).
> 4. During execute of the query, take the power on the machine running
> the Derby server.
> 5. Your program will hang "infinite".
> I will post a short repro program that can be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
