Download
Getting Started
Members
Projects
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
More
Community
Marketplace
Events
Planet Eclipse
Newsletter
Videos
Participate
Report a Bug
Forums
Mailing Lists
Wiki
IRC
How to Contribute
Working Groups
Automotive
Internet of Things
LocationTech
Long-Term Support
PolarSys
Science
OpenMDM
Toggle navigation
Bugzilla – Attachment 148937 Details for
Bug 282012
[Build] Core LRG: 256Mb object allocation requires increase from 512 to 1024 Mb or 2048 on 64-bit JVM
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
Log In
[x]
|
Terms of Use
|
Copyright Agent
[patch]
Decrease maxmemory to 1024 from 1536 to accomidate 2GB RAM machines - introduce max.heap.memory variable that power users can override
282012_add_max_heap_memory_variable_for_core_lrg.patch (text/plain), 2.33 KB, created by
Michael OBrien
on 2009-10-06 16:03:20 EDT
(
hide
)
Description:
Decrease maxmemory to 1024 from 1536 to accomidate 2GB RAM machines - introduce max.heap.memory variable that power users can override
Filename:
MIME Type:
Creator:
Michael OBrien
Created:
2009-10-06 16:03:20 EDT
Size:
2.33 KB
patch
obsolete
>Index: foundation/eclipselink.core.test/build.properties >=================================================================== >--- foundation/eclipselink.core.test/build.properties (revision 5439) >+++ foundation/eclipselink.core.test/build.properties (working copy) >@@ -9,6 +9,12 @@ > > # Edit this property when you would like to override the java version during testing > javac.version=1.5 >+ >+# Edit this property to increase the maxMemory heap memory used by the tests if you get an OutOfMemoryException - use JConsole.exe to triage the memory spike at the end of the test >+# 282012: On a 64-bit JVM - The XML processing at the end of the testing requires at least 1536 >+# Note: on a legacy XP OS with 4GB ram - the max is 1536 - use of 2048 will cause [junit] [WARN ] Unable to acquire some virtual address space - reduced from 2048 to 1908MB. >+# The current default is 1024m = 1GB (the LC "m" is required") >+max.heap.memory=1024m > > # Do not edit the properties below. > eclipselink.plugins=../../plugins >Index: foundation/eclipselink.core.test/build.xml >=================================================================== >--- foundation/eclipselink.core.test/build.xml (revision 5439) >+++ foundation/eclipselink.core.test/build.xml (working copy) >@@ -264,8 +264,8 @@ > <mkdir dir="${eclipselink.core.test}/${run.dir}"/> > <mkdir dir="${eclipselink.core.test}/${report.dir}"/> > <!-- 282012: On a 64-bit JVM - The XML processing at the end of the testing requires at least 1536 --> >- <!-- Note: on a legacy XP OS with 2GB ram - the max is 1536 - use of 2048 will cause [junit] [WARN ] Unable to acquire some virtual address space - reduced from 2048 to 1908MB. --> >- <junit printsummary="yes" failureproperty="junit.failed" fork="yes" showoutput="true" maxmemory="1536m" dir="${eclipselink.core.test}/${run.dir}"> >+ <!-- Note: on a legacy XP OS with 4GB ram - the max is 1536 - use of 2048 will cause [junit] [WARN ] Unable to acquire some virtual address space - reduced from 2048 to 1908MB. --> >+ <junit printsummary="yes" failureproperty="junit.failed" fork="yes" showoutput="true" maxmemory="${max.heap.memory}" dir="${eclipselink.core.test}/${run.dir}"> > <jvmarg value="-Declipselink.logging.level=${logging.level}"/> > <jvmarg value="-Ddb.driver=${db.driver}"/> > <jvmarg value="-Ddb.url=${db.url}"/>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 282012
:
140502
|
148364
|
148417
|
148648
| 148937