db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4856) Add thread dump information when derby crash
Date Thu, 02 Dec 2010 22:00:11 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966299#action_12966299
] 

Kathey Marsden commented on DERBY-4856:
---------------------------------------


Hi Lily,

I see what you mean about ExceptionUtil.java. I think the short story is that that it should
not have ever been used by the engine.  David's original comment said:

"DERBY-838: Establish an internationalization framework for the network
client.

Added a new shared directory and shared packages.  These shared packages
are only used by the derbyclient.jar until we establish a shared code framework"

I recall conversations long ago that until we figured out how to really handle common code,
things that would be potentially  good to share would be put under shared, but only be used
by client until the whole framework was worked out. Unfortunately this history was lost when
during the LOB work too years later, ExceptionUtil obviously looked very convenient for this
 engine work, but we should probably file a bug to take references to ExceptionUtil out of
the engine.





> 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.


Mime
View raw message