[
https://issues.apache.org/jira/browse/DERBY-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-4037:
----------------------------------
thanks for the new report. It looks like the test needs some more tweaking.
The new output shows that the wait at end did allow for the system to free up a
bunch of pages, vs. the previous
report so I don't think there is a real problem here. But the test really
wants the free'ing to come
in the loop so that the subsequent insert can use the free'd pages of the
previously committed
deleted. For some reason this machine must not allow as concurrent background
thread work
as other platforms. I'll think about how best to change the test.
> On Z/OS storetests/st_reclaim_longcol.java fails with a large number of pages
> ------------------------------------------------------------------------------
>
> Key: DERBY-4037
> URL: https://issues.apache.org/jira/browse/DERBY-4037
> Project: Derby
> Issue Type: Bug
> Components: Store, Test
> Affects Versions: 10.3.3.0
> Environment: java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz6460sr3-20081108_01(SR3))
> IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 z/OS s390x-64
> jvmmz6460-20081107_254
> J9VM - 20081105_025433_BHdSMr
> JIT - r9_20081031_1330
> GC - 20081027_AB)
> JCL - 20081106_01
> Reporter: Kathey Marsden
> Assignee: Mike Matrigali
>
> On Z/OS 64 bit (haven't checked 32bit) st_reclaim_loncol fails with a large
> number of pages.
> ********* Diff file derbyall/storeall/storetests/st_reclaim_longcol.diff
> *** Start: st_reclaim_longcol jdk1.6.0 storeall:storetests 2009-01-23
> 14:20:49 ***
> 3a4,6
> > Test failed, expected less than 150 pages - count is:
> > free pages : 258
> > allocated pages: 2047
> Test Failed.
> *** End: st_reclaim_longcol jdk1.6.0 storeall:storetests 2009-01-23
> 14:25:07 ***
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
