[jira] Commented: (DERBY-4856) Add thread dump information when derby crash

["Lily Wei (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981122#action_12981122 ] 

Lily Wei commented on DERBY-4856:
---------------------------------

Check in svn #1058404 for part_3_3g patch with space/tab changes and AuthenticationTest.java change.
It is possible the database.isActive() information could need more work. Please watch that for me. When running suites.all with ibm jvm, there are left over javacore* files. I still need to do clean up work. More information is needed to find out which tests create the javacore*file. There are two ways to clean up the javacore* files - create teardown() method to clean up the javacore* files or set the flag by calling 
setSystemProperty("derby.stream.error.extendedDiagSeverityLevel","50000")

Derby3980DeadlockTest might not always produce deadlock error and it is not part of nightly run test.

Thank Kathey so much for keep helping me review and write this part of fix. Thank Knut for giving very helpful tips in IRC and everywhere else.  Hopefully, the javacore* files will not cause the machine to run out of disk space. Post-commit reviews still welcome. :)


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