[
https://issues.apache.org/jira/browse/DERBY-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744009#action_12744009
]
Knut Anders Hatlen commented on DERBY-4323:
-------------------------------------------
The log shows that a timeout exception was thrown instead of a deadlock
exception. The lock table does however show that there is a deadlock, so either
the deadlock detection algorithm must have failed to detect it, or the deadlock
didn't happen until after the deadlock detection algorithm had completed. My
guess is on the latter. If it happens again, we could try to increase the
deadlock timeout in the test (currently two seconds) to give it more time to
get into the expected state before deadlock detection is performed.
> test failure in lang.ErrorMessageTest with IBM iseries IBM 1.5
> --------------------------------------------------------------
>
> Key: DERBY-4323
> URL: https://issues.apache.org/jira/browse/DERBY-4323
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.5.2.0
> Environment: IBM iseries, OS: AS/400; OS version: V5R4M0, IBM 1.5
> (1.5.0_13-b05)
> Reporter: Myrna van Lunteren
> Priority: Minor
> Attachments: error-stacktrace.out, ErrorMessageTest_derby.log
>
>
> There was this error during the 10.5.2.0 test run - when the ErrorMessageTest
> was run by itself later there was no problem, and neither did this show up
> during the ibm 1.6 run:
> 1)
> testDeadlockTimeout(org.apache.derbyTesting.functionTests.tests.lang.ErrorMessageTest)junit.framework.ComparisonFailure:
> Not a deadlock expected:<...001> but was:<...XL2>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
