You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2010/07/09 15:05:50 UTC
[jira] Created: (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
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
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
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.
-
You can reply to this email to add a comment to the issue online.
[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
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4740:
----------------------------------
Affects Version/s: 10.7.0.0
Component/s: Test
> 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.0.0
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.