Java Monitor and Increasing Java Memory

Hello,

We are using:

Java 1.5
WebObjects 5.3.1
Mac OS X Server (Tiger) 10.4.7

We used to use:

Java 1.4.2
WebObjects 5.2.4
Solaris 10

We are trying to increase the virtual machines memory using the -Xms  
and -Xmx commands.  We are sending in the command line arguments - 
Xmx256m -Xms128m via the additional arguments box in Java monitor.   
The problem is that it doesn't seem to be running with those  
additional arguments.  Running the commandps -axwww | grep CMS3.0 shows:

java -XX:NewSize=2m -Xmx64m -Xms32m -DWORootDirectory=/System - 
DWOLocalRootDirectory= -DWOUserDirectory=/System/Library/WebObjects/ 
JavaApplications/wotaskd.woa -DWOEnvClassPath= - 
DWOApplicationClass=Application -DWOPlatform=MacOS - 
Dcom.webobjects.pid=6994 -Xmx256m -Xms128m -classpath WOBootstrap.jar  
com.webobjects._bootstrap.WOBootstrap -WOPort 2005 -WOCachingEnabled  
YES -WODebuggingEnabled YES -WOOutputPath /wo_apps/logs/CMS3.0-1 - 
WOAutoOpenInBrowser NO -WOAutoOpenClientApplication NO - 
WOLifebeatInterval 30 -WOLifebeatEnabled YES - 
WOLifebeatDestinationPort 1085 -WOAdaptor WODefaultAdaptor - 
WOWorkerThreadCount 8 -WOListenQueueSize 128 -WOWorkerThreadCountMin  
16 -WOWorkerThreadCountMax 256 -NSProjectSearchPath () - 
WOSessionTimeOut 3600 -WOApplicationName CMS3.0 -WOMonitorEnabled YES  
-WONoPause YES

It indicates that the application is running with the default values  
for a WO program.  I also checked the Sun docs for Java 1.5 and the  
usage of the -Xms and -Xmx flags have not changes.  I don't think it  
is a Java problem and have come to the conclusion that I am doing  
something wrong with Java Monitor.  Is there any reason anyone can  
see why Java Monitor isn't passing my commands?

Regards,
Jeff