Develop Reference

MAVEN_OPTS ignored when setting java heap size

How is this possible? I do not understand linux correctly because I do not
know how this can happen. I believe there is something else happening here as im trying to set the max heap size to 1G and it is failing
The MAVEN_OPTS specify a heap of 1024m but the maven command fails because the heap is 4096m. The machine is 32 bit with 6G installed
Memory
$free -h
total used free shared buffers cached
Mem: 5.8G 3.8G 2.0G 186M 351M 2.1G
-/+ buffers/cache: 1.3G 4.4G
Swap: 5.8G 0B 5.8G
Maven
echo $MAVEN_OPTS
-Xms512m -Xmx1024m -XX:MaxPermSize=1024m
$ mvn -version
Invalid maximum heap size: -Xmx4096m
The specified size exceeds the maximum representable size.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Java
java -version
java version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) Server VM (build 25.111-b14, mixed mode)
Linux
uname -a 102-Ubuntu SMP Tue Aug 11 14:28:35 UTC 2015 i686 i686 i686 GNU/Linux

Set again with below and try:
Linux:
export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=1024m"
Windows
set MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=1024m"

I just ran across this same error, and the solution was provided to my via this blog post. In the post, it is stated;
Check mvn.bat: the MAVEN_OPTS is passed as JVM parameter directly:
SET MAVEN_JAVA_EXE="%JAVA_HOME%\bin\java.exe" %MAVEN_JAVA_EXE%
%MAVEN_OPTS% -classpath %CLASSWORLDS_JAR%
"-Dclassworlds.conf=%M2_HOME%\bin\m2.conf" "-Dmaven.home=%M2_HOME%"
%CLASSWORLDS_LAUNCHER% %MAVEN_CMD_LINE_ARGS%
If we run set MAVEN_OPTS="-Xmx1024M -XX:MaxPermSize=256M",the previous
command would be replaced with %MAVEN_JAVA_EXE% "-Xmx1024M
-XX:MaxPermSize=256M" ...
If we run java "-Xmx1024M -XX:MaxermSize=256M" -version: we will see
same error message.
The solution is simple: We can run: set "MAVEN_OPTS=-Xmx1024M
-XX:MaxPermSize=256M" or remove the double quotes completely: set MAVEN_OPTS=-Xmx1024M -XX:MaxPermSize=256M
The value of MAVEN_OPTS would be with no surrounding double quotes.
This certainly addressed my issue.

Invoking jMeter from the command line with 64-bit directive loses the class

We were running 32-bit JDK and jMeter 2.6, and were running into heap memory issues when simulating 8000 users spread out over the course of an hour.
We upgraded to 64-bit Java, and jMeter 2.12.
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)
When we run from the command line requesting a 4Gb heap (the server has 32Gb), we receive the message that the initial heap size is too large.
set JVM_ARGS="-Xms4G -Xmx4G -XX:NewSize=512m -XX:MaxNewSize=1G" jmeter.sh
When we add the option -d64 to JVM_ARGS, we no longer receive the error about the heap size, but it no longer finds the class
set JVM_ARGS="-d64 -Xms4G -Xmx4G -XX:NewSize=512m -XX:MaxNewSize=1G" jmeter.sh
Pointing it to the directory seems to have no effect
set JVM_ARGS="-d64 -Xms4G -Xmx4G -XX:NewSize=512m -XX:MaxNewSize=1G -cp mypath" jmeter.sh

Looking into jmeter.sh it seems you're trying to run JMeter on Linux or MacOSX. I believe you need to remove set word (or replace it with export)
Given you have correct java executable in PATH providing -d64 option shouldn't be required. Something like:
JAVA_HOME=/path/to/64-bit/jdk && export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH && export PATH
You can edit jmeter script and amend the following lines:
HEAP="-Xms512m -Xmx512m"
NEW="-XX:NewSize=128m -XX:MaxNewSize=128m"
"Telling" Jmeter to use Concurrent Mark Sweep (CMS) Garbage Collector can also improve JMeter-side performance greatly. The relevant line is:
-XX:+UseConcMarkSweepGC
See 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure article for more information on getting the most from your JMeter installation.

Unable to increase heap size for JMeter on Mac OSX

Is there a way to increase heap size of JMeter in Mac OSX? I have tried editing the jmeter.bat file, but it didn't help.
I edited the jmeter.sh file to add JVM_ARGS="-Xms3072m -Xmx3072m" jmeter.sh
I tried the following also
#!/bin/bash
heap_size='3072m'
JAVA_CMD="java -Xms$heap_size -Xmx$heap_size" meter`
as suggested in this link increase the memory allocated to jmeter in ubuntu linux
Does any one know how to do it in Mac OSX. I have java version as follows:
java version 1.6.0_65
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)`
on OSX 10.9.4

As per JMeter Performance and Tuning Tips
Default JMeter java configuration comes with 512 Mo and very little GC tuning.
First ensure you set -Xmx option value to a reasonable value regarding your test requirements.
Then change MaxNewSize option in jmeter file to respect the original ratio between MaxNewSize and -Xmx.
Java Virtual Machine parameters can be tuned in jmeter script file which lives under /bin folder of JMeter installation. So
Open jmeter script with text editor of your choice
Look for the line HEAP="-Xms512m -Xmx512m"
Change minimum and maximum values according to your desires
Save the file and make sure that you're executing jmeter, not jmeter.sh
If you're looking for once-only command-line JVM args overriding you can call JMeter main jar directly without any shell script wrappers as
java -Xms1G -Xmx3G -jar ApacheJMeter.jar
The command above assumes that you're invoking it from /bin folder of your JMeter installation.

I installed JMeter on my Mac via Homebrew and found that I needed to create a new setenv.sh file containing the configurations, as specified in the jmeter file instructions:
Do not set the variables in this script. Instead put them into a script
setenv.sh in JMETER_HOME/bin to keep your customisations separate.
I found that the JMETER_HOME path was /usr/local/Cellar/jmeter/5.4.3/libexec/ as opposed to /usr/local/Cellar/jmeter/5.4.3/ which I initially tried unsuccessfully.
So, in the end, I had
/usr/local/Cellar/jmeter/5.4.3/libexec/bin/setenv.sh conatining:
HEAP="-Xms2g -Xmx4g -XX:MaxMetaspaceSize=512m"
NEW="-XX:NewSize=512m -XX:MaxNewSize=1024m"
Which I verified was working from the following in the jmeter.log file:
INFO o.a.j.JMeter: Max memory =4294967296

Unable to start Weblogic 10.3

I am using Windows 8 Pro 64 bit, Java 1.6 64 bit. I am trying to start Weblogic with following memory args (setDomainEnv.cmd):
set USER_MEM_ARGS=-Xmx2048m -XX:PermSize=512m -XX:MaxPermSize=1024m
But i'm getting an error:
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
Those mermory args are required to deploy the app, so i can't lower it (physical mermory installed - 8 GB).

Combined with -Xmx512M use -d64 to make sure you're running 64-bit VM. On a 64-bit machine I thought for sure I was running 64-bit virtual machine, but no. After installing 64-bit Java the -d64 option works and -Xmx allows much larger memory sizes.
java -d64 -Xmx512M mypackage.Test
Please see the below link for more solutions...
Could not reserve enough space for object heap

I am running weblogic 81. I had min=1024 and max =1024m with 4gb or RAM. 64bit processor and 32 bit java. I tried to increase the min/max value, it did not work. So, I changed the min/max to 512m and 1024m respectively. Thn it started to work.

When i installed for first time, the SOA environment developed mode, needed to do that:set JAVA_OPTIONS=%JAVA_OPTIONS% set DEFAULT_MEM_ARGS=-Xms512m -Xmx768m set PORT_MEM_ARGS=-Xms768m -Xmx1536m But over time, it shows me the same error and tube to make the following change: set JAVA_OPTIONS=%JAVA_OPTIONS% set DEFAULT_MEM_ARGS=-Xms512m -Xmx512m set PORT_MEM_ARGS=-Xms512m -Xmx512m But I'm still not sure why this happens.

unable to set xmx beyond 4gb on system having 8gb RAM

I need to set
ANT_OPTS=-Xms1024m -Xmx6144m -XX:PermSize=1024m -XX:MaxPermSize=1024m
JAVA_OPTS=-Xms1024m -Xmx6144m -XX:PermSize=1024m -XX:MaxPermSize=1024m
I have a system with 8gb(recently upgraded from 4 gb)
But once i set the ant opts to above said value I am not able to run any of my ant targets and I get the following error
[ERROR] Argument error: -Xmx6144m
[ERROR] Specified maximum heap size (6144 MB) is larger than the address space on this platform (4 GB).
[WARN ] -XX:PermSize=1024m is not a valid VM option. Ignoring
[WARN ] -XX:MaxPermSize=1024m is not a valid VM option. Ignoring
Could not create the Java virtual machine.
This indicates the Java that I have on my system
java version "1.6.0_20"
Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Oracle JRockit(R) (build R28.1.0-123-138454-1.6.0_20-20101014-1351-windows-x86_64, compiled mode)
and I am running a Windows 7 on Intel Core 2 Duo 3Ghz processor and 8GB RAM.
PS: I did Google for the error and it was one of my first such occurrences where I did not get any links pointing to the specific solution.

As discussed in the comments:
It would seem that your ANT installation is using a 32-bit JVM. While a 64-bi JVM is in your PATH ANT doesn't obey the JVM in your PATH, it first looks at JAVA_HOME. You can verify this by running $JAVA_HOME/bin/java -version.
You can update your environment to set JAVA_HOME to the 64-bit version or change the ANT script to always use a specific version of Java.

The error message appears to be suggesting the platform is 32-bit. I imagine you can't actually use 4 GB.
I would try installing the 64-bit version of Java and using that.
For the HotSpot JVM I would expect to see
$ java -mx30g -version
java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)