Re: additional arguments and java heap

Yup, that worked.  Thanks so much.  While I was already using the 'm' 
byte metric, I think monitor did not like the '='.  I was just 
following the example in the Monitor docs under the help tab.  Either I 
misunderstood it, or it ain't quite right.

-b


On Mar 22, 2005, at 1:45 PM, Denis Stanton wrote:

>
> On 23/03/2005, at 5:06 AM, Sacha Mallais wrote:
>
>> On Mar 22, 2005, at 7:52 am, Anthony Brian Arthur wrote:
>>
>>> When I start the deployed app without specifying Xms & Xmx memory 
>>> range, it starts fine.  However, if I specify these args it does 
>>> not.  Would anyone know why this happens?
>>>
>>> I am using args -Xms=256 -Xmx=1024, and earlier I got it work.  
>>> Later, I bumped it up to -Xmx=2048 (or 4096 not sure) which is when 
>>> I started having this problem.
>>>
>> I wonder if you need the "m" after that, since you seem to be 
>> specifying a max heap size of 1024 _bytes_.
>
> I'm quite sure you need the M.  I think it has to be M, not m, though 
> I haven't tried the lower case.
> There shouldn't be an '=' in there.  Try
> 	-Xms64M -Xmx256M
>
>
> Denis Stanton
> [email protected]
> Home:  (09) 533 0391
> mobile: 021 1433622