db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fernanda Pizzorno (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1910) OutOfMemoryError happens when jdbcapi/_Suite.junit was executed as DerbyNetClient (in jvm1.4.2)
Date Tue, 03 Oct 2006 11:50:21 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1910?page=all ]

Fernanda Pizzorno updated DERBY-1910:
-------------------------------------

    Attachment: derby-1910.diff
                derby-1910.stat

The problem was being caused by some of the tests that kept a reference to a connection object
which prevented this objects from being garbage collected. The attached patch (derby-1910.diff)
fixes that problem.

I monitored the memory usage of the junit.textui.TestRunner JVM by using the jstat with and
without this patch. Without the patch the memory usage kept increasing, and with the patch
the JVM was able to garbage collect and the memory usage stayed under 17000Kb. I have successfully
run jdbcapi, derbynetmats and derbynetclientmats with this patch. Can someone please review
it?

> OutOfMemoryError happens when jdbcapi/_Suite.junit was executed as DerbyNetClient (in
jvm1.4.2)
> -----------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1910
>                 URL: http://issues.apache.org/jira/browse/DERBY-1910
>             Project: Derby
>          Issue Type: Bug
>         Environment: naka@rufelza:~/derby/test/20061001_2$ cat /proc/version 
> Linux version 2.6.12-1-386 (horms@tabatha.lab.ultramonkey.org) (gcc version 4.0.2 20050917
(prerelease) (Debian 4.0.1-8)) #1 Tue Sep 27 12:41:08 JST 2005
> naka@rufelza:~/derby/test/20061001_2$ java -version
> java version "1.4.2_10"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)
>            Reporter: Tomohito Nakayama
>         Assigned To: Fernanda Pizzorno
>         Attachments: derby-1910.diff, derby-1910.stat
>
>
> I found this phenomena at my environment.
> naka@rufelza:~/derby/test/20061001_2$ runNetClientTest.sh jdbcapi/_Suite.junit
> /home/naka/derby/dev/trunk/jars/sane/derby.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbytools.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbynet.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyclient.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyrun.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyTesting.jar:
> /home/naka/derby/dev/trunk/tools/java/jakarta-oro-2.0.8.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_de_DE.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_es.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_fr.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_it.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_ja_JP.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_ko_KR.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_pt_BR.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_zh_CN.jar:
> /home/naka/derby/dev/trunk/jars/sane/derbyLocale_zh_TW.jar:
> /home/naka/derby/dev/trunk/tools/java/junit.jar:
> /home/naka/derby/dev/trunk/tools/java/db2jcc.jar:
> /home/naka/derby/dev/trunk/tools/java/db2jcc_license_c.jar:.
> console.encoding:null file.encoding:ISO-8859-1 derby.ui.codeset: null
> *** Start: _Suite jdk1.4.2_10 DerbyNetClient 2006-10-01 14:19:52 ***
> Initialize for framework: DerbyNetClient
> startServer = false. Bypass server startup
> java -Duser.language=en -Duser.country=US -Dderby.system.home=/home/naka/derby/test/20061001_2/DerbyNetClient/_Suite
-Dderby.infolog.append=true -Dframework=DerbyNetClient -Djava.security.manager -Djava.security.policy=/home/naka/derby/test/20061001_2/derby_tests.policy
-DderbyTesting.clientjar=file:/home/naka/derby/dev/trunk/jars/sane/ -DderbyTesting.codejar=file:/home/naka/derby/dev/trunk/jars/sane/
-DderbyTesting.testjar=file:/home/naka/derby/dev/trunk/jars/sane/ -DderbyTesting.codedir=/home/naka/derby/dev/trunk/jars/sane
-DderbyTesting.serverhost=localhost -DderbyTesting.clienthost=localhost junit.textui.TestRunner
org.apache.derbyTesting.functionTests.tests.jdbcapi._Suite 
> The test should be running...
> About to execute: diff.exec( outName = /home/naka/derby/test/20061001_2/DerbyNetClient/_Suite.out,outDir
= /home/naka/derby/test/20061001_2/DerbyNetClient,pwDiff = java.io.PrintWriter@12f0999,testOutName
= _Suite,frameworkMaster = DerbyNetClient,jvmName = jdk14,iminor = 4,useprocess = true,systemdiff
= false,canondir = null,canonpath = null)
> 0 add
> > .......................E....
> > There was 1 error:
> > 1) testClobAsciiWrite3Param(org.apache.derbyTesting.functionTests.tests.jdbcapi.LobStreamsTest)java.lang.OutOfMemoryError
> > FAILURES!!!
> > Tests run: 847,  Failures: 0,  Errors: 1
> Test Failed.
> *** End:   _Suite jdk1.4.2_10 DerbyNetClient 2006-10-01 14:22:01 ***
> This seems to be same as the error which was recorded in next test result.
> http://www.multinet.no/~solberg/public/Apache/DerbyJvm1.4/Limited/testSummary-451360.html
> Comparing results at http://www.multinet.no/~solberg/public/Apache/index.html, 
> this phenomena seems to happen when test was executed with jvm 1.4.2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message