Showing results for 
Show  only  | Search instead for 
Did you mean: 
Level 2

Lax Files - Java Max Heap Configuration

Hello there,

In most of our installations we use the following parameter to specify the max heap size:

# -------------------------------------
# the maximum heap size for the Java VM

It has some strange behavior if it comes to higher values, following are some examples:

Works fine:
cmd: "…\jre\bin\java.exe" -Xms10485760 -Xmx1073741824 -classpath …
cmd: "…\jre\bin\java.exe" -Xms10485760 -Xmx2146435072 -classpath …

wrong behavior - passing on NO value: (and ongoing till 4096m)
cmd: "…\jre\bin\java.exe" -Xms10485760 -classpath …

wrong behavior - passing on wrong values:
cmd: "…\jre\bin\java.exe" -Xms10485760 -Xmx1048576 -classpath… ongoing values passing on the value minus 4GB
cmd: "…\jre\bin\java.exe" -Xms10485760 -Xmx2147483647 -classpath…all values over 2GB passing on 2GB

The following parameter has no problems with any of the above.
# -----------------------------
# Behebt eventuelle Probleme mit der 3D-Darstellung und PC-Anywhere

Why is there a interpretation of the given value and not a simple passing through?
Does the first parameter have any benefits or should we generally use the additional parameter?

Edit: Tested on a 64Bit machine with an pure 64Bit Windows Installer (also tested with 64Bit and 32Bit installer ... but there are obvious other limitations)

Labels (1)
0 Kudos
(1) Reply
Level 3

Yes this has confused me as well.
Looks like the limit is the limit for a java int.

I think this should be fixed as a product defect.
Abandon use of and and expect the values set in
Interpret the values properly and cope with "k", "K", "m", "M", "g" , "G" (as specified in the commands for java.exe) and have no upper limit.
0 Kudos