[
https://issues.apache.org/jira/browse/DERBY-4986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988100#action_12988100
]
Kim Haase commented on DERBY-4986:
----------------------------------
Thanks very much, Lily. Reading the release note, I have a couple of questions
about the difference in behavior between the Oracle and IBM JVMs.
"Oracle jvm will print thread dump information with error severity higher than
session error and IBM jvm will print out thread dump information and a
javacore."
Does this mean that the Oracle JVM pays attention to the severity levels the
user sets, but the IBM JVM does not? Or does "with error severity higher than
session error" apply to both JVMs?
Also,
"Users can find thread dump information on derby.log and users of ibm jvm will
have more diagostic information in the javacore* file."
Does this mean that the contents of derby.log are the same for both the Oracle
and IBM JVMs, but that IBM users will see additional information in the
javacore file?
Maybe it would be helpful if you attached a sample of the derby.log, too.
Thanks again!
> 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
>
>
> 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.
