[
https://issues.apache.org/jira/browse/DERBY-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4986:
----------------------------
Attachment: derby.log
threaddump.txt
javacore.20110128.085450.3872.0001.txt
Thanks Kim.
Oracle jvm and IBM jvm will both pay attention to the severity levels and print
thread dump information to derby.log. IBM users will see addtional information
in the javacore file.
I include three files in the attachment.
1. derby.log that include thread dump information
2. threaddump.txt Extract the thread dump information from derby.log.
3. javacore.20110128.085450.3872.0001.txt The javacore file created by ibm jvm.
> Document the new property derby.stream.error.extendedDiagSeverityLevel for
> thread dump and extend diagnostic information
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4986
> URL: https://issues.apache.org/jira/browse/DERBY-4986
> Project: Derby
> Issue Type: Task
> Components: Documentation
> Affects Versions: 10.7.1.1
> Reporter: Lily Wei
> Assignee: Kim Haase
> Priority: Minor
> Fix For: 10.8.0.0
>
> Attachments: derby.log, javacore.20110128.085450.3872.0001.txt,
> threaddump.txt
>
>
> With new behavior on thread dump and extended diagnostic information, it is
> needed to document the new property. Please refer to DERBY-4856.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
