Knut Anders Hatlen <[email protected]> writes: > Rick Hillegas <[email protected]> writes: > >> I saw an error in ClobMemTest when it ran along with the rest of the >> JUnit tests, invoked by this command: >> >> java -XX:MaxPermSize=128M -Xmx512m >> -DderbyTesting.oldReleasePath=/Users/rh161140/derby/upgradeReleases >> -DderbyTesting.oldVersionsPath=/Users/rh161140/derby/upgradeReleases/startingPoints >> junit.textui.TestRunner >> org.apache.derbyTesting.functionTests.suites.All >> >> However, I did not see the error when I ran ClobMemTest standalone: >> >> java -Xmx512m >> -DderbyTesting.oldReleasePath=/Users/rh161140/derby/upgradeReleases >> junit.textui.TestRunner >> org.apache.derbyTesting.functionTests.tests.memory.ClobMemTest >> >> Here is the error. Anyone else seeing it? > > I haven't seen it, but it has happened in the nightly regression tests > too. I've posted a comment on DERBY-4477, which is the issue that added > the test case.
See also the new DERBY-4531, which was the root cause for this problem. I'll be committing a fix for ClobMemTest as soon as I have run new regressions .
