[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4856:
----------------------------
Attachment: ContextManager.java
Thanks Knut and Kathey.
For phrase one, the goal is to use ExceptionUtil.dumpThread() in
AssertFailure.java. AssertFailure.java is in shared/common/sanity for insane
build.
For phrase two, the goal is to use ExceptionUtil.dumpThread() in ContextManager
for engine. ExceptionUtil is in shared/common/error which is an existing class
for derby.jar and derbyclient.jar. I am including ContextManaer.java now to
help me understand does it fit into the David's concern on DERBY-289
https://issues.apache.org/jira/browse/DERBY-289?focusedCommentId=12415429&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12415429.
If phrase two's change is only to ContextManager.java(working progress) which
uses ExceptionUtil.java and ExceptionUtil.java is an existing class, do I still
need to introduce code in java/engine/org/apache/derby/iapi/services/info to
have similar class? I would think it is safe to use since it is an existing
class on shared/common/error that derby.jar and derbyclient.jar both had.
> 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: ContextManager.java, 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.
