[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981252#action_12981252
]
Lily Wei commented on DERBY-4856:
---------------------------------
Thanks Knut for reviewing. I will add the comment to explain why the system
property has to be set for AuthenticationTest. When I run suites.all with 1.6
ibm jvm, it created 145 javacore* files. I review most of them and most of them
come from AuthenticationTest for getConnection that will get error/SQLException
with negative tests. So, it makes sense for the thread dump information and
diagnostic information. However, we really don't want to have too many left
over javacore* files after test run. So, I set it in baseSuite() to trigger not
producing such behavior. I will look into wrap the test in a
SystemPropertyTestSetup to see whether it is more appropriate.
> 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
> Fix For: 10.8.0.0
>
> Attachments: ContextManager.java, corruptdb.zip, derby-4856-1a.diff,
> DERBY-4856-part_1_1a.diff, DERBY-4856_part_2_2a.diff,
> DERBY-4856_part_2_2b.diff, DERBY-4856_part_3_1a.diff,
> DERBY-4856_part_3_2a.diff, DERBY-4856_part_3_3a.diff,
> DERBY-4856_part_3_3b.diff, DERBY-4856_part_3_3c.diff,
> DERBY-4856_part_3_3d.diff, DERBY-4856_part_3_3e.diff,
> DERBY-4856_part_3_3g.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.
