db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4740) On Mac OSX 10.6 suites.All fails with Exception in thread "main" java.lang.OutOfMemoryError: PermGen space even with -XX:MaxPermSize=128M
Date Thu, 24 Feb 2011 21:54:38 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Myrna van Lunteren updated DERBY-4740:
--------------------------------------

    Urgency: Low
     Labels: derby_triage10_8  (was: )

> On Mac OSX 10.6 suites.All fails with Exception in thread "main" java.lang.OutOfMemoryError:
PermGen space even with -XX:MaxPermSize=128M
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4740
>                 URL: https://issues.apache.org/jira/browse/DERBY-4740
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.7.1.1
>         Environment: Mac OS X 10.6 
> java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-10M3065)
> Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode)
>            Reporter: Kathey Marsden
>              Labels: derby_triage10_8
>
> On Mac OS X 10.6 I ran suites.All with:
> java  -Dderby.tests.trace=true -XX:MaxPermSize=128M -Xmx1024M -Xms512M -DderbyTesting.oldReleasePath=/Users/kmarsden/Derby/svn/svnreleases/jars
junit.textui.TestRunner org.apache.derbyTesting.functionTests.suites.All 2>&1 | tee
rjall.out
> It failed in the upgrade tests with:
> testDMDconnClosed used 9 ms  Test upgrade done.
> Test upgrade from: 10.2.2.0, phase: POST UPGRADE
> .
> noConnectionAfterHardUpgrade used 4 ms  Test upgrade done.
> Test upgrade from: 10.3.1.4, phase: CREATE
> Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
> I was able to work around the issue by setting -XX:MaxPermSize=256M  but think perhaps
the upgrade tests may be leaking class loaders.
> PhaseChanger.teardown() is careful to shutdown each database but not the Derby system,
so it could be the class loaders are not getting garbage collected.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message