[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932967#action_12932967
]
Bryan Pendleton commented on DERBY-4856:
----------------------------------------
+1 to placing this information in a file of some sort.
derby.log is a reasonable suggestion.
Another idea is create a separate file JUST for this this crash information.
Since it's similar in notion to a "crash dump" file, how about a uniquely
generated name for a standalone "dump" file of some sort, as in:
derby_minidump_YYMMDD_n.txt
Where the YYMMDD is today's date, and the 'N' is
a number incremented each time we produce a dump on
that date.
A nicely packaged standalone dump file produced on a system crash
would provide a very helpful tool for users to interact with the
community when trying to diagnose Derby problems.
> 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.
