Re: java.lang.outofmemory
Re: java.lang.outofmemory
- Subject: Re: java.lang.outofmemory
- From: Robert Walker <email@hidden>
- Date: Wed, 8 Mar 2006 09:14:21 -0500
| There is one additional option that can be used to ensure/override the memory setting for all instances (even if they are not included in the arguments in JavaMonitor).
On the aggregate target there is a JVM_OPTIONS key in Expert View. Entering the memory settings here will include them in the launch arguments of every instance.
Example: java -XX:NewSize=2m -Xmx64m -Xms32m -DWORootDirectory="/System" -DWOLocalRootDirectory="" -DWOUserDirectory="/Users/robertwalker/Source/MyWOApp/build" -DWOEnvClassPath="" -DWOApplicationClass=Application -DWOPlatform=MacOS -Dcom.webobjects.pid=4128 -Xmx256m -classpath WOBootstrap.jar com.webobjects._bootstrap.WOBootstrap -WOPort 55555 On Mar 8, 2006, at 7:51 AM, Paul Lynch wrote:
On 7 Mar 2006, at 23:10, Randy Wigginton wrote: At the risk of appearing foolish to a lot of people… where do I adjust the memory setting in XCode? I’ve gone to the target, and pasted the command line changes into the “pure java” field. But my startup parameters don’t change. Where does it really belong?
If you set it per instance using JavaMonitor, it goes in Instance Settings, Additional Arguments, with all the other command line arguments.
In the project (Xcode 2.2), inspect the Executable for your app, and use the Arguments tab. Like the example Jacky Gagnon used:
-Xms64m -Xmx300m
Paul
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden