From derby-dev-return-83090-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Tue Dec 07 20:11:35 2010 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 86211 invoked from network); 7 Dec 2010 20:11:35 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Dec 2010 20:11:35 -0000 Received: (qmail 2659 invoked by uid 500); 7 Dec 2010 20:11:35 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 2632 invoked by uid 500); 7 Dec 2010 20:11:35 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 2591 invoked by uid 99); 7 Dec 2010 20:11:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Dec 2010 20:11:35 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Dec 2010 20:11:32 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB7KBBDC001507 for ; Tue, 7 Dec 2010 20:11:11 GMT Message-ID: <23041452.34271291752670996.JavaMail.jira@thor> Date: Tue, 7 Dec 2010 15:11:10 -0500 (EST) From: "Kathey Marsden (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4856) Add thread dump information when derby crash MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968935#action_12968935 ] Kathey Marsden commented on DERBY-4856: --------------------------------------- Thanks Lily for the patch. For the new engine ExceptionUtil, I don't think the field threadDump is needed or used. The reflection call should use the ThreadDump in engine, not the shared one. I think then it will be fine for the engine ThreadDump class to keep the original name, ThreadDump. In ContextManager, there seem to be some javadoc formatting issues with the new getErrorCode method, which might better be callse dgetErrorSeverity. I would add a comment that errors that are not Standard or SQLExcetions are not handled at this time. ] > Add thread dump information when derby crash > -------------------------------------------- > > Key: DERBY-4856 > URL: https://issues.apache.org/jira/browse/DERBY-4856 > Project: Derby > Issue Type: Bug > Components: Services > Reporter: Lily Wei > Assignee: Lily Wei > Priority: Minor > Fix For: 10.8.0.0 > > Attachments: ContextManager.java, corruptdb.zip, derby-4856-1a.diff, DERBY-4856-part_1_1a.diff, DERBY-4856_part_2_2a.diff, derby.log > > > On system crash or session ending error, Derby should dump as much information as possible. Such as: forcing a javacore if possible or at least thread dump and system environment information. This should only occur if a running session crashes not on boot error due to fail recovery etc. > The IBM jvm provides a way to programmatically dump a javacore. i.e. com.ibm.jvm.Dump.JavaDump() And, the SUN jvm will force a thread dump using the Unsafe class and there may be a better way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.