db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5137) Enable or remove Derby3980DeadlockTest
Date Wed, 16 Mar 2011 18:11:29 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007599#comment-13007599
] 

Kathey Marsden commented on DERBY-5137:
---------------------------------------

I think the testing in T_RawStoreFactory etc, is to use extendedDiagSeverity to suppress the
thread dump for certain errors so I think it is good to have a test for when it is used to
generate the thread dump for diagnostics and a Deadlock case would be best as I think that
is how it will normally be used.  

I think moving the extendedDiagSeverity test to DeadlockDetectionTest would be fine and don't
see any rush to do this. Thank you again for buddy testing and all you do for Derby.



> 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

Mime
View raw message