[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932892#action_12932892
]
Knut Anders Hatlen commented on DERBY-4856:
-------------------------------------------
I'd prefer that we don't change the behaviour of
StandardException.printStackTrace(), as that may be confusing to the users and
may also make the output from the applications noisy and harder to read. To me
it sounds sufficient to dump this information to derby.log and not include the
thread dump in the exception itself. What about adding the code to
ContextManager.cleanupOnError() instead? That's where the writing of errors to
derby.log happens.
> 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.
