[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965861#action_12965861
]
Kathey Marsden commented on DERBY-4856:
---------------------------------------
I think the point of the move is to make them available for insane builds so
they can be used by the engine on a crash, so if it cannot be in shared, I
guess instead of moving the SanityManager code, there will have to be separate
new code for producing thread dumps in
java/engine/org/apache/derby/iapi/services/info. It would be good to include
comments in both explaining that any bug fixes will likely have to be fixed in
both places.
> 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.
