[
https://issues.apache.org/jira/browse/DERBY-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-4863:
----------------------------------
Component/s: (was: Network Server)
JDBC
Urgency: Normal
Labels: derby_triage10_8 (was: )
Summary: Derby update operation with setQueryTimeout does not timeout
until the locks are released. (was: Derby update operation does not timeout
until the locks are released.)
Triage for 10.8. Marking normal urgency and changed component to JDBC as the
reproduction is with embedded.
> Derby update operation with setQueryTimeout does not timeout until the locks
> are released.
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-4863
> URL: https://issues.apache.org/jira/browse/DERBY-4863
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.6.2.1
> Environment: windows 7, jdk 1.5.0_22, derby 10.6.2.1
> Reporter: Florin Herinean
> Labels: derby_triage10_8
> Attachments: StatementTimeout.java
>
>
> Derby update statements do not timeout until the (write) locks are released.
> The scenario involves 2 threads starting 2 separate transactions/connections,
> each of them attempting to update the same row. The first thread starts the
> transaction, locks the row (via update) then waits 40 seconds. The second
> thread is started 5 seconds later and it has a 5 seconds timeout set on the
> statement. Upon attempting to update the same row as the first thread, it
> times out after 35 seconds (40 - 5) and not after the expected 5 seconds as
> specified in the statement timeout.
> A test case is attached.
> Oracle and DB2 behaves as expected.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
