[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4856:
----------------------------
Attachment: DERBY-4856_part_3_3g_2a.diff
Thanks Kathey for giving her blessing for DERBY-4856_part_3_3g_1a.diff patch.
There is only one javacore* file left after running suites.all with ibm 1.6
jvm. The test runs clean. The file is from LockInterruptTest. Add property to
avoid thread dump and diagnostic information with DERBY-4856_part_3_3g_2a.diff
patch. Please review the code.
> 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.
