db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3503) Change stress.multi to dump thread stacks before killing off testers with jdk 1.5 and higher
Date Fri, 07 Mar 2008 21:55:46 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kathey Marsden updated DERBY-3503:
----------------------------------

    Derby Info: [Patch Available]

Tests passed except for known issues.  I verified stack traces printed for failed stress.multi
runs and ran stress.multi on jdk 1.4.2 to make sure it wasn't affected.  I'll check this in
Monday morning if I don't hear anything.

 

> 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.


Mime
View raw message