[
https://issues.apache.org/jira/browse/DERBY-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577072#action_12577072
]
Kathey Marsden commented on DERBY-3503:
---------------------------------------
Knut said ...
>don't think I would have bothered unwrapping the >PrivilegedActionException
>and the InvocationTargetException, as the >original exception is in the chain
>and its stack trace is printed anyway. Not >a big deal, but it would perhaps
>make the code a bit cleaner.
hmmm the reason I was unwrapping it was because I was not seeing the chained
exception print. It would be hard to reproduce now. Maybe that was with jdk
1.4.2, but anyway I think I will leave it as is. Thanks Knut for the review.
> 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, 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.
