[
https://issues.apache.org/jira/browse/DERBY-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604094#action_12604094
]
Kathey Marsden commented on DERBY-1764:
---------------------------------------
I am sorry I did not have a chance to have a close look at your test today. I
will tomorrow if someone else doesn't beat me to it.
I think your 20 second delay is for deadlock timeouts which default to 20
seconds:
http://db.apache.org/derby/docs/10.0/manuals/tuning/perf78.html
Below are the properties for the test which should be setup.
derby.locks.deadlockTimeout=3
derby.locks.waitTimeout=5
derby.language.logStatementText=true
derby.storage.keepTransactionLog=true
You can use SystemPropertyTestSetup to setup the properties.
> Rewrite stress.multi as a JUnit test
> ------------------------------------
>
> Key: DERBY-1764
> URL: https://issues.apache.org/jira/browse/DERBY-1764
> Project: Derby
> Issue Type: Test
> Components: Test
> Reporter: Knut Anders Hatlen
> Assignee: Erlend Birkenes
> Attachments: DERBY-1764-Review.diff
>
>
> Currently, stress.multi consists of a number of sql scripts that are run in
> ij. It often fails with cryptic error messages, and since it uses ij, there
> is often no stack trace. It would be very useful to rewrite the test in JUnit
> so that we can get better error messages and stack traces when it fails.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
