[
https://issues.apache.org/jira/browse/DERBY-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004785#comment-13004785
]
Kristian Waagan commented on DERBY-5097:
----------------------------------------
Haven't spent much time on this, but if this is easily reproducible it may be
better to simply use a non-zero timeout value for the utility class that
fetches/verifies the statistics (see line 142 in the test class).
As Rick suggests, it may very well be that the background thread is never
allowed to run (it is supposed to be started immediately) due to differences in
the OS scheduling policy. It would also be good to enable logging/tracing and
compare the output between a working and a failing run.
>
> testMTSelect(org.apache.derbyTesting.functionTests.tests.store.AutomaticIndex
> StatisticsMultiTest)junit.framework.AssertionFailedError: failed to get
> statisti cs for table MTSEL (#expected=2, timeout=0) on AIX IBM JDK 1.5
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5097
> URL: https://issues.apache.org/jira/browse/DERBY-5097
> Project: Derby
> Issue Type: Bug
> Components: Services
> Environment: $ java -version
> java version "1.5.0"
> Java(TM) 2 Runtime Environment, Standard Edition (build pap32dev-20100813
> (SR12
> FP1 ))
> IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 AIX ppc-32 j9vmap3223-20100808
> (JIT
> enabled)
> J9VM - 20100629_60535_bHdSMr
> JIT - 20100623_16197_r8
> GC - 20100211_AA)
> JCL - 20100813
> Reporter: Kathey Marsden
>
> I need to check if this is intermittent, but noticed the following failure
> running suites.All on AIX with IBM 1.5.
> 1)
> testMTSelect(org.apache.derbyTesting.functionTests.tests.store.AutomaticIndex
> StatisticsMultiTest)junit.framework.AssertionFailedError: failed to get
> statisti
> cs for table MTSEL (#expected=2, timeout=0)
> Index statistics for MTSEL
> : <no stats>
> expected:<2> but was:<0>
> at
> org.apache.derbyTesting.junit.IndexStatsUtil.getStatsTable(IndexStats
> Util.java:236)
> at
> org.apache.derbyTesting.functionTests.tests.store.AutomaticIndexStati
> sticsMultiTest.verifyStatistics(AutomaticIndexStatisticsMultiTest.java:143)
> at
> org.apache.derbyTesting.functionTests.tests.store.AutomaticIndexStati
> sticsMultiTest.testMTSelect(AutomaticIndexStatisticsMultiTest.java:87)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:79)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:
> 112)
> FAILURES!!!
> Tests run: 11518, Failures: 1, Errors: 0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
