Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 63157 invoked from network); 14 Jan 2011 03:47:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Jan 2011 03:47:13 -0000 Received: (qmail 29760 invoked by uid 500); 14 Jan 2011 03:47:13 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 29561 invoked by uid 500); 14 Jan 2011 03:47:11 -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 29553 invoked by uid 99); 14 Jan 2011 03:47:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jan 2011 03:47:09 +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; Fri, 14 Jan 2011 03:47:07 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p0E3kkF7007319 for ; Fri, 14 Jan 2011 03:46:46 GMT Message-ID: <7241525.362011294976806252.JavaMail.jira@thor> Date: Thu, 13 Jan 2011 22:46:46 -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=12981622#action_12981622 ] Lily Wei commented on DERBY-4856: --------------------------------- Thanks Kathey for reviewing. At LockInterruptTest.runWaiter() line 150 with ps.executeUpdate, the test receive an interrupt and raise an error/exception "ERROR 08000: Connection closed by unknown interrupt". I think this is a negative test case again. So, I set the flag to turn off thread dump and diagnostic information. > 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-4856_part_2_2b.diff, DERBY-4856_part_3_1a.diff, DERBY-4856_part_3_2a.diff, DERBY-4856_part_3_3a.diff, DERBY-4856_part_3_3b.diff, DERBY-4856_part_3_3c.diff, DERBY-4856_part_3_3d.diff, DERBY-4856_part_3_3e.diff, DERBY-4856_part_3_3g.diff, DERBY-4856_part_3_3g_1a.diff, DERBY-4856_part_3_3g_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.