[
https://issues.apache.org/jira/browse/DERBY-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007597#comment-13007597
]
Lily Wei commented on DERBY-5137:
---------------------------------
extendedDiagSeverity test exists for T_RawStoreFactory etc. The special policy
file is added to allow creating javadoc* file for ibm jvm. When doing the test,
I did encounter issue in turn of thread dump information did not show up in
derby.log. However, due to need more synchronization between the two threads,
it might not be the most ideal case to add extenedDiagSeverity to
Derby3980DeadlockTest. it is fine with me to remove this test. Is it okay to
add the extenedDiagSeverity to DeadlockDetectionTest? I am still working on
buddy testing JDBC 4.1. If it is okay to add generating javadoc* file testing
for extendedDiagSeverity to DeadlockDectioinTest. If it is okay, I will add it
after finish buddy testing. Thanks!
> Enable or remove Derby3980DeadlockTest
> --------------------------------------
>
> Key: DERBY-5137
> URL: https://issues.apache.org/jira/browse/DERBY-5137
> Project: Derby
> Issue Type: Improvement
> Affects Versions: 10.8.0.0
> Reporter: Kathey Marsden
>
> As part of early work on DERBY-3980, I checked in an unrun test for this
> issue when I was working on it a long time ago, Derby3980DeadlockTest.
> I verified it does pass now but maybe the new DeadLockDetectionTest provides
> the same coverage.
> This this test should be enabled or removed if it adds no additional
> coverage.
> Derby3980DeadlockTest does seem to have some testing for
> extendedDiagSeverity level and
> diagProperties.setProperty("derby.stream.error.extendedDiagSeverityLevel",
> "30000");
> One thing to note is that it now, with the IBM JVM, I think correctly will
> print
> JVMDUMP010I Java dump written to ...
> I am surprised though not to see a thread dump in derby.log, so maybe there
> is an issue with extendedDiagSeverity that needs to be looked at too.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
