[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] JAVA_MAXHEAP_ARGUMENT parameter causing error (Windows)
- Date: Fri, 01 Apr 2011 11:55:13 -0400
- From: Matthew Farrellee <matt@xxxxxxxxxx>
- Subject: Re: [Condor-users] JAVA_MAXHEAP_ARGUMENT parameter causing error (Windows)
On 03/31/2011 01:51 PM, Ziliang Guo wrote:
Klaus: The -Xmx parameter needs to have a value after it, like -Xmx100m
or something, to be a valid parameter to the JVM. The Windows config
file has just -Xmx in the JAVA_MAXHEAP_ARGUMENT config knob and not a
value after it. That could potentially cause problems as the code does
not seem to actually check if there is a numerical value after -Xmx. We
probably should set a default. The -classpath parameter may also be an
issue but I have not looked into it.
This is wrong. JAVA_MAXHEAP_ARGUMENT is designed to provide the name of
the argument to the JVM for specifying the max heap. It is not designed
to also include the amount of memory for the max heap.
Greg's suggestion of "JAVA_MAXHEAP_ARGUMENT = " is golden. Honestly, the
assumptions that made JAVA_MAXHEAP_ARGUMENT useful are no longer valid.