Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 36396 invoked from network); 1 Dec 2010 18:09:34 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Dec 2010 18:09:34 -0000 Received: (qmail 34229 invoked by uid 500); 1 Dec 2010 18:09:34 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 34208 invoked by uid 500); 1 Dec 2010 18:09:33 -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 34201 invoked by uid 99); 1 Dec 2010 18:09:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Dec 2010 18:09:33 +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, 01 Dec 2010 18:09:33 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB1I9DIS014074 for ; Wed, 1 Dec 2010 18:09:13 GMT Message-ID: <21175280.50921291226953088.JavaMail.jira@thor> Date: Wed, 1 Dec 2010 13:09:13 -0500 (EST) From: "Knut Anders Hatlen (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 [ https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965772#action_12965772 ] Knut Anders Hatlen commented on DERBY-4856: ------------------------------------------- I think this is OK as long as the classes are only used by the sane jars. If you plan to use the classes in the production jars too, you should be aware of the discussion in DERBY-289, which raises some concerns about having code in the shared packages. > 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 > Attachments: corruptdb.zip, derby-4856-1a.diff, DERBY-4856-part_1_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.