[DERBY-2029] Query timeout does not take effect if server machine crashes

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.2.2.0, 10.3.1.4
• Component/s: JDBC, Network Client
• Labels: derby_triage10_9
• Environment: Solaris 10, JDK 1.5
• Urgency: Normal
• Issue & fix info: Repro attached
• Assignee: Unassigned
• Reporter: Olav Sandstaa
• Created: 01/Nov/06 21:13
• Updated: 20/Feb/12 22:18

Description

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.