Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 38781 invoked from network); 17 Nov 2010 04:08:08 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 17 Nov 2010 04:08:08 -0000 Received: (qmail 857 invoked by uid 500); 17 Nov 2010 04:08:40 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 767 invoked by uid 500); 17 Nov 2010 04:08:39 -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 753 invoked by uid 99); 17 Nov 2010 04:08:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Nov 2010 04:08:39 +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; Wed, 17 Nov 2010 04:08:37 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oAH48FM9020636 for ; Wed, 17 Nov 2010 04:08:15 GMT Message-ID: <6624262.136941289966895356.JavaMail.jira@thor> Date: Tue, 16 Nov 2010 23:08:15 -0500 (EST) From: "Lily Wei (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=12932806#action_12932806 ] Lily Wei commented on DERBY-4856: --------------------------------- The changes included: 1. Move ThreadDump.java from java/shared/org/apache/derby/shared/common/sanity to java/shard/org/apache/derby/shared/common/error 2. move dumpThreads method from AssertFailure to ExceptionUtil 3. Add printStackTrace to StandardException when severity >= ExceptionSeverity.SESSION_SEVERITY You can find thread dump information in derby.log for corruptdb database Hope this is helpful. > 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 > Priority: Minor > Attachments: corruptdb.zip, derby-4856-1a.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.