Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1258767067.1204905226249.JavaMail.jira@brutus>
Date: Fri, 7 Mar 2008 07:53:46 -0800 (PST)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-3503) Change stress.multi to dump thread
 stacks before killing off testers with jdk 1.5 and higher
In-Reply-To: <1893722288.1204822978499.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kathey Marsden reassigned DERBY-3503:
-------------------------------------

    Assignee: Kathey Marsden

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