[
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_2a.diff
Thanks to IRC discussion with Kathey and Knut. This is the prototype for
checking whether database is active or it is okay to trace thread dump
information in ContextManager.cleanupOnError on top of part_3_1a patch. The
change includes:
1. cleanupOnError takes two parameters: error and isdbactive. If
isdbactive, it will print out threadudmp info and diagnosis information for ibm
jvm
2. The guide line to get isdbactive information is to just pass the
Boolean value when it make sense, get it from the isactive information from the
database associated with the object, get it from the isactive Boolean value
from the database associated with LanguageConnectionContext, or the isactive
value from EmbedPooledConnection value.
The patch passed Suites.all and derbyall for sun jvm. However, it hangs on
replication tests for ibm jvm such as ReplicationRun_Local in
ReplicationRun_Local.connectPing somewhere near
conn=DriverManager.getConnection(dbURL);
The patch is ready for review. Thank you for reviewing in advance.
> 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.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.
