The second one should win, though you can print Runtime.getRuntime
().maxMemory() in your app startup to be sure. You can also edit
your woa startup script and remove the first -Xmx (which is probably
where that is coming from).
ms
On Aug 30, 2006, at 12:53 PM, Marc Respass wrote:
Hi All,
I'm getting out of memory exceptions in my app. I do need to go
through it and see if there is anything I can do to manage memory
better, but until then, I tried increasing the memory of the JVM. I
did it by adding
-Xmx256M -Xms128m to the Additional Arguments section of the apps
configuration in Monitor. When I check the running processes using
ps axwww | grep Xmx
I see my app but it has two occurrences as you can see below.
I'm questioning which of those is taken. I would think that the
arguments are checked as they are encountered and that the last one
is the one used but I don't know any way to be sure.
Can anyone confirm that the Additional Arguments section in Monitor
is the right place to put that and that it is the last argument
that takes effect?
Thanks
Marc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/mschrag%
40mdimension.com
