[
https://issues.apache.org/jira/browse/DERBY-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-3503:
----------------------------------
Attachment: derby-3503_diff.txt
Attached is an initial patch for this issue, but it is not ready for commit. I
still need to run the full suite.
For JDK 1.5 or higher we log the thread dump to the log before interrupting
the testers if they don't shut down normally.
I had to add two permissions for derbyTesting.jar/classes so that we can call
getAllStackTraces:
+ permission java.lang.RuntimePermission "getStackTrace";
+ permission java.lang.RuntimePermission "modifyThreadGroup";
Thanks
Kathey
> Change stress.multi to dump thread stacks before killing off testers with jdk
> 1.5 and higher
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-3503
> URL: https://issues.apache.org/jira/browse/DERBY-3503
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3503_diff.txt
>
>
> Jdk 1.5 introduced Thread.getAllStackTraces() which can be used to print a
> thread dump programatically. The test stress.multi kills off its testers if
> it reaches a deadlock or the testers can't complete on their own. It would be
> helpful in this case to get a thread dump automatically. The code could only
> be enabled for jdk 1.5 and higher.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
