Paul Lynch

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

Robert Walker

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

Pascal Robert

To add more memory when developing with Eclipse/WOLips, open the Run Dialog (right-click on your project -> Run As -> Open Run dialog...). Locate the run configuration for your project, open the Arguments tab and put the memory arguments in the VM arguments field.