[
https://issues.apache.org/jira/browse/DERBY-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4856:
----------------------------
Attachment: DERBY-4856_part_3_3d.diff
After running derbyall and suites.all with ibm 1.6 jvm, I made the following
adjustment and attach 3d patch:
1. Check whether database is null at
TransactionResourceImple.handleException as sometimes the database can be null
and we will not want to print any thread dump or diagnostic information
2. Modify MaxLogNumberRecovery.java to set
derby.stream.error.extendedDiagSeverityLevel to 50000 so no thread dump or
diagnostic information as test exceed the max log file number.
3. Revert the change for SimpleTest.java since the flag value is being
used in Derby3980DeadlockTest and MaxLogNumberRecovery.
Derbyall and suites.all does not have any unexpected failure with ibm 1.6 jvm.
I am running with sun jvm now. The patch is ready for review.
> 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.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.
