Jmeter Issue 32bit vs 64bit Physical RAM swap Space


Following issue in Jmeter:

# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 32756 bytes for ChunkPool::allocate
# Possible reasons:
# The system is out of physical RAM or swap space
# In 32 bit mode, the process size limit was hit
# Possible solutions:
# Reduce memory load on the system
# Increase physical memory or swap space
# Check if swap backing store is full
# Use 64 bit Java on a 64 bit OS
Solution: 
Change the value as mention below in /apache-jmeter-2.9/bin/jmeter.sh 
JAVA_HOME=/JDK1.7.51-64/jdk1.7.0_51/
PATH=/JDK1.7.51-64/jdk1.7.0_51/bin:$PATH
export PATH
export JAVA_HOME
JVM_ARGS="-d64 -Xms1024m -Xmx50000m -server"
/JDK1.7.51-64/jdk1.7.0_51/bin/java $JVM_ARGS -jar `dirname $0`/ApacheJMeter.jar "$@"

Verify it: Run the /apache-jmeter-2.9/bin/jmeter.sh

jmeter.log will generated with below message:

INFO - jmeter.util.JMeterUtils: Setting Locale to en
INFO - jmeter.JMeter: Loading user properties from: /apache-jmeter-2.9/bin/user.properties
INFO - jmeter.JMeter: Loading system properties from: /apache-jmeter-2.9/bin/system.properties INFO - jmeter.JMeter: Copyright (c) 1998-2013 The Apache Software Foundation
INFO - jmeter.JMeter: Version 2.9 r1437961
INFO - jmeter.JMeter: java.version=1.7.0_51
INFO - jmeter.JMeter: java.vm.name=Java HotSpot(TM) 64-Bit Server VM INFO - jmeter.JMeter: os.name=SunOS
INFO - jmeter.JMeter: os.arch=amd64
INFO - jmeter.JMeter: os.version=5.10
INFO - jmeter.JMeter: file.encoding=ISO646-US
INFO - jmeter.JMeter: Default Locale=English
INFO - jmeter.JMeter: JMeter Locale=English
INFO - jmeter.JMeter: JMeterHome=/apache-jmeter-2.9
INFO - jmeter.JMeter: user.dir =/apache-jmeter-2.9/bin
INFO - jmeter.JMeter: PWD =/apache-jmeter-2.9/bin
INFO - jmeter.JMeter: IP: 10.145.84.100 Name: tutorialbyexample.com FullName: tutorialbyexample.com
INFO - jmeter.JMeter: Loaded icon properties from org/apache/jmeter/images/icon.properties WARN - jmeter.gui.action.ActionRouter: java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. 2015/04/21 16:03:31 FATAL - jmeter.JMeter: An error occurred: java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. at java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:207)

Whereas java.vm.name=Java HotSpot(TM) 64-Bit Server VM indicate we have configure it 64 bit and we can increased the max heap size more than 3 GB which is limited for 32 bit jvm.

Have good day ahead!!!

No comments:

Post a Comment