db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4856) Add thread dump information when derby crash
Date Wed, 17 Nov 2010 04:08:15 GMT

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


Mime
View raw message