[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4856:
----------------------------
Attachment: derby.log
derby-4856-1a.diff
Thanks to Kathey. I am able to construct first attempt to add thread dump on
insane build for embedded server.
I am puzzling on whether the StandardException.printStackTrace(PrintWriter s)
for severity >= ExceptionSeverity.SESSION_SEVERITY is the best place to print
out thread dump or place like ErrorStringBuilder.stackTrace is better.
Personally, I think it shouldn't be that much noise to put in
StandardException.printStackTrace(PrinterWriter s) Any opinion is welcome.
Please review the code and give me your opinion. Thanks.
> 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.
