Which aspects test when using JMeter

[Angus Ferguson]

Hi,

I have built a JMeter test plan with Graphs and sumary reports, it shows me the the max time it takes to load the min, the average. I want to build a document like this:

When more than 100 users visits the website concurrently. Action: Increase memory for that day
When more than 100 users visits the website and stay all of tehm for longer than 10 minutes: Action ....

Which are the most important scenarios which should I have into account when stressing a website, this one is for ecommerce and has 50 visits per day a the moment.

I mean for example if the internet go slower till 256 per sec then do this.....

I order to check every case is maybe a good idea to do it use BeanShell Assertion, for example:

FileOutputStream out = new FileOutputStream(sugarTrendsLoadTest, true);
String newline = System.getProperty("line.separator");
int code = Integer.parseInt(ResponseCode);
switch (code) {
  case 200:
      out.write("Response code is 200".getBytes());
      out.write(newline.getBytes());
      out.write("Working fine");
      break;
  case 500:
      out.write("Response code is 500".getBytes());
      out.write("Internal server error. Contact your server provider or check your server manually");
      break;
  default:
      break;

}

In this case which are the codes I should have into account?.

I found this link: codes. For example, could someone answer this:

No Response 204

Server has received the request but there is no information to send back, and the client should stay in the same document view. This is mainly to allow input for scripts without changing the document at the same time.

When getting this message, what is supposed the user or a administrator with knowledge of programming should do?

Are there codes for things like check when the memory is collapsing and other situation to have into account?

I hope I have explained the situation I have now.

Any advice please?

Regards, ISaac

[Dmitri Tikhanski]

You don't need to re-invent the wheel, JMeter automatically saves response message in its .jtl results file.

1442430997331,407,HTTP Request,200,OK,Thread Group 1-1,text,true,1591,1,1,407
1442430997764,215,HTTP Request,404,Not Found,Thread Group 1-1,text,false,1622,1,1,214
1442430997979,219,HTTP Request,405,Method Not Allowed,Thread Group 1-1,,false,189,1,1,219

Code: 200, Message: OK
Code: 404, Message: Not Found
Code: 405, Message: Method not allowed.

You can control what and how JMeter saves in its results file by modifying properties which names start from jmeter.save.saveservice. See jmeter.properties file in /bin folder of your JMeter installation for default values and Apache JMeter Properties Customization Guide for advanced information on JMeter properties and ways of working with them.

[Angus Ferguson]

I modified the jmeter.properties liker this, sorry I just put the whole file, I deleted all the coments jmeter.save.saveservice, and I will run it tonight but I need to know where the resulting file will be placed.
Could someone tell me in which line of this file is that especified, please?

################################################################################
# Apache JMeter Property file
################################################################################
##   Licensed to the Apache Software Foundation (ASF) under one or more
##   contributor license agreements.  See the NOTICE file distributed with
##   this work for additional information regarding copyright ownership.
##   The ASF licenses this file to You under the Apache License, Version 2.0
##   (the "License"); you may not use this file except in compliance with
##   the License.  You may obtain a copy of the License at
## 
##       http://www.apache.org/licenses/LICENSE-2.0
## 
##   Unless required by applicable law or agreed to in writing, software
##   distributed under the License is distributed on an "AS IS" BASIS,
##   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
##   See the License for the specific language governing permissions and
##   limitations under the License.

################################################################################
#
#                      THIS FILE SHOULD NOT BE MODIFIED
#
# This avoids having to re-apply the modifications when upgrading JMeter
# Instead only user.properties should be modified:
# 1/ copy the property you want to modify to user.properties from jmeter.properties
# 2/ Change its value there
#
################################################################################

#Preferred GUI language. Comment out to use the JVM default locale's language.
#language=en

# Additional locale(s) to add to the displayed list.
# The current default list is: en, fr, de, no, es, tr, ja, zh_CN, zh_TW, pl, pt_BR
# [see JMeterMenuBar#makeLanguageMenu()]
# The entries are a comma-separated list of language names
#locales.add=zu

# Netscape HTTP Cookie file
cookies=cookies

#---------------------------------------------------------------------------
# File format configuration for JMX and JTL files
#---------------------------------------------------------------------------

# Properties:
# file_format          - affects both JMX and JTL files
# file_format.testplan - affects JMX files only
# file_format.testlog  - affects JTL files only
#
# Possible values are:
# 2.1 - initial format using XStream
# 2.2 - updated format using XStream, with shorter names

# N.B. format 2.0 (Avalon) is no longer supported

#---------------------------------------------------------------------------
# XML Parser
#---------------------------------------------------------------------------

# XML Reader(Parser) - Must implement SAX 2 specs
xml.parser=org.apache.xerces.parsers.SAXParser

# Path to a Properties file containing Namespace mapping in the form
# prefix=Namespace
# Example:
# ns=http://biz.aol.com/schema/2006-12-18
#xpath.namespace.config=

#---------------------------------------------------------------------------
# SSL configuration
#---------------------------------------------------------------------------

## SSL System properties are now in system.properties

# JMeter no longer converts javax.xxx property entries in this file into System properties.
# These must now be defined in the system.properties file or on the command-line.
# The system.properties file gives more flexibility.

# By default, SSL session contexts are now created per-thread, rather than being shared.
# The original behaviour can be enabled by setting the JMeter property:
#https.sessioncontext.shared=true

# Default HTTPS protocol level:
#https.default.protocol=TLS
# This may need to be changed here (or in user.properties) to:
#https.default.protocol=SSLv3

# List of protocols to enable. You may have to select only a subset if you find issues with target server.
# This is needed when server does not support Socket version negotiation, this can lead to:
# javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
# java.net.SocketException: Connection reset
# see https://issues.apache.org/bugzilla/show_bug.cgi?id=54759
#https.socket.protocols=SSLv2Hello SSLv3 TLSv1

# Control if we allow reuse of cached SSL context between iterations
# set the value to 'false' to reset the SSL context each iteration
#https.use.cached.ssl.context=true

# Start and end index to be used with keystores with many entries
# The default is to use entry 0, i.e. the first
#https.keyStoreStartIndex=0
#https.keyStoreEndIndex=0

#---------------------------------------------------------------------------
# Look and Feel configuration
#---------------------------------------------------------------------------

#Classname of the Swing default UI
#
# The LAF classnames that are available are now displayed as ToolTip text
# when hovering over the Options/Look and Feel selection list.
#
# You can either use a full class name, as shown above,
# or one of the strings "System" or "CrossPlatform" which means
#  JMeter will use the corresponding string returned by UIManager.get<name>LookAndFeelClassName()

# LAF can be overridden by os.name (lowercased, spaces replaced by '_')
# Sample os.name LAF:
#jmeter.laf.windows_xp=javax.swing.plaf.metal.MetalLookAndFeel

# Failing that, the OS family = os.name, but only up to first space:
# Sample OS family LAF:
#jmeter.laf.windows=com.sun.java.swing.plaf.windows.WindowsLookAndFeel

# Mac apparently looks better with the System LAF
jmeter.laf.mac=System

# Failing that, the JMeter default laf can be defined:
#jmeter.laf=System

# If none of the above jmeter.laf properties are defined, JMeter uses the CrossPlatform LAF.
# This is because the CrossPlatform LAF generally looks better than the System LAF.
# See https://issues.apache.org/bugzilla/show_bug.cgi?id=52026 for details
# N.B. the laf can be defined in user.properties.

# LoggerPanel display
# default to false
#jmeter.loggerpanel.display=false

# Enable LogViewer Panel to receive log event even if closed
# Enabled since 2.12
# Note this has some impact on performances, but as GUI mode must
# not be used for Load Test it is acceptable
#jmeter.loggerpanel.enable_when_closed=true

# Error/Fatal Log count display
# defaults to true
#jmeter.errorscounter.display=true

# Max characters kept in LoggerPanel, default to 80000 chars
# O means no limit
#jmeter.loggerpanel.maxlength=80000

# Toolbar display
# default:
#jmeter.toolbar.display=true
# Toolbar icon definitions
#jmeter.toolbar.icons=org/apache/jmeter/images/toolbar/icons-toolbar.properties
# Toolbar list
#jmeter.toolbar=new,open,close,save,save_as_testplan,|,cut,copy,paste,|,expand,collapse,toggle,|,test_start,test_stop,test_shutdown,|,test_start_remote_all,test_stop_remote_all,test_shutdown_remote_all,|,test_clear,test_clear_all,|,search,search_reset,|,function_helper,help
# Toolbar icons default size: 22x22. Available sizes are: 22x22, 32x32, 48x48
#jmeter.toolbar.icons.size=22x22

# Icon definitions
# default:
#jmeter.icons=org/apache/jmeter/images/icon.properties
# alternate:
#jmeter.icons=org/apache/jmeter/images/icon_1.properties

#Components to not display in JMeter GUI (GUI class name or static label)
# These elements are deprecated: HTML Parameter Mask,HTTP User Parameter Modifier, Webservice (SOAP) Request
not_in_menu=org.apache.jmeter.protocol.http.modifier.gui.ParamModifierGui, HTTP User Parameter Modifier, org.apache.jmeter.protocol.http.control.gui.WebServiceSamplerGui

# Number of items in undo history
# Feature is disabled by default (0)
# Set it to a number > 0 (25 can be a good default)
# The bigger it is, the more it consumes memory
#undo.history.size=0

#---------------------------------------------------------------------------
# Remote hosts and RMI configuration
#---------------------------------------------------------------------------

# Remote Hosts - comma delimited
remote_hosts=127.0.0.1
#remote_hosts=localhost:1099,localhost:2010

# RMI port to be used by the server (must start rmiregistry with same port)
#server_port=1099

# To change the port to (say) 1234:
# On the server(s)
# - set server_port=1234
# - start rmiregistry with port 1234
# On Windows this can be done by:
# SET SERVER_PORT=1234
# JMETER-SERVER
#
# On Unix:
# SERVER_PORT=1234 jmeter-server
#
# On the client:
# - set remote_hosts=server:1234

# Parameter that controls the RMI port used by the RemoteSampleListenerImpl (The Controler)
# Default value is 0 which means port is randomly assigned
# You may need to open Firewall port on the Controller machine
#client.rmi.localport=0

# When distributed test is starting, there may be several attempts to initialize
# remote engines. By default, only single try is made. Increase following property
# to make it retry for additional times
#client.tries=1

# If there is initialization retries, following property sets delay between attempts
#client.retries_delay=5000

# When all initialization tries was made, test will fail if some remote engines are failed
# Set following property to true to ignore failed nodes and proceed with test 
#client.continue_on_fail=false

# To change the default port (1099) used to access the server:
#server.rmi.port=1234

# To use a specific port for the JMeter server engine, define
# the following property before starting the server:
#server.rmi.localport=4000

# From JMeter 2.3.1, the jmeter server creates the RMI registry as part of the server process.
# To stop the server creating the RMI registry:
#server.rmi.create=false

# From JMeter 2.3.1, define the following property to cause JMeter to exit after the first test
#server.exitaftertest=true

# Prefix used by IncludeController when building file name
#includecontroller.prefix=

#---------------------------------------------------------------------------
#         Logging Configuration
#---------------------------------------------------------------------------

# Note: JMeter uses Avalon (Excalibur) LogKit

# Logging Format
# see http://excalibur.apache.org/apidocs/org/apache/log/format/PatternFormatter.html

#
# Default format:
#log_format=%{time:yyyy/MM/dd HH:mm:ss} %5.5{priority} - %{category}: %{message} %{throwable}
# \n is automatically added to the end of the string
#
# Predefined formats in the JMeter LoggingManager:
#log_format_type=default
#log_format_type=thread_prefix
#log_format_type=thread_suffix
# default is as above
# thread_prefix adds the thread name as a prefix to the category
# thread_suffix adds the thread name as a suffix to the category
# Note that thread name is not included by default, as it requires extra processing.
#
# To change the logging format, define either log_format_type or log_format
# If both are defined, the type takes precedence
# Note that these properties cannot be defined using the -J or -D JMeter
# command-line flags, as the format will have already been determined by then
# However, they can be defined as JVM properties

#Logging levels for the logging categories in JMeter.  Correct values are FATAL_ERROR, ERROR, WARN, INFO, and DEBUG
# To set the log level for a package or individual class, use:
# log_level.[package_name].[classname]=[PRIORITY_LEVEL]
# But omit "org.apache" from the package name.  The classname is optional.  Further examples below.

log_level.jmeter=INFO
log_level.jmeter.junit=DEBUG
#log_level.jmeter.control=DEBUG
#log_level.jmeter.testbeans=DEBUG
#log_level.jmeter.engine=DEBUG
#log_level.jmeter.threads=DEBUG
#log_level.jmeter.gui=WARN
#log_level.jmeter.testelement=DEBUG
#log_level.jmeter.util=WARN
#log_level.jmeter.protocol.http=DEBUG
# For CookieManager, AuthManager etc:
#log_level.jmeter.protocol.http.control=DEBUG
#log_level.jmeter.protocol.ftp=WARN
#log_level.jmeter.protocol.jdbc=DEBUG
#log_level.jmeter.protocol.java=WARN
#log_level.jmeter.testelements.property=DEBUG
log_level.jorphan=INFO
	

#Log file for log messages.
# You can specify a different log file for different categories via:
# log_file.[category]=[filename]
# category is equivalent to the package/class names described above

# Combined log file (for jmeter and jorphan)
#log_file=jmeter.log
# To redirect logging to standard output, try the following:
# (it will probably report an error, but output will be to stdout)
#log_file=

# Or define separate logs if required:
#log_file.jorphan=jorphan.log
#log_file.jmeter=jmeter.log

# If the filename contains  paired single-quotes, then the name is processed
# as a SimpleDateFormat format applied to the current date, for example:
#log_file='jmeter_'yyyyMMddHHmmss'.tmp'

# N.B. When JMeter starts, it sets the system property:
#    org.apache.commons.logging.Log
# to
#    org.apache.commons.logging.impl.LogKitLogger
# if not already set. This causes Apache and Commons HttpClient to use the same logging as JMeter

# Further logging configuration
# Excalibur logging provides the facility to configure logging using
# configuration files written in XML. This allows for such features as
# log file rotation which are not supported directly by JMeter.
#
# If such a file specified, it will be applied to the current logging
# hierarchy when that has been created.
# 
#log_config=logkit.xml

#---------------------------------------------------------------------------
# HTTP Java configuration
#---------------------------------------------------------------------------

# Number of connection retries performed by HTTP Java sampler before giving up
#http.java.sampler.retries=10
# 0 now means don't retry connection (in 2.3 and before it meant no tries at all!)

#---------------------------------------------------------------------------
# Commons HTTPClient configuration
#---------------------------------------------------------------------------

# define a properties file for overriding Commons HttpClient parameters
# See: http://hc.apache.org/httpclient-3.x/preference-api.html
# Uncomment this line if you put anything in httpclient.parameters file
#httpclient.parameters.file=httpclient.parameters


# define a properties file for overriding Apache HttpClient parameters
# See: TBA
# Uncomment this line if you put anything in hc.parameters file
#hc.parameters.file=hc.parameters

# Following properties apply to both Commons and Apache HttpClient

# set the socket timeout (or use the parameter http.socket.timeout) 
# for AJP Sampler and HttpClient3 implementation.
# Note for HttpClient3 implementation it is better to use GUI to set timeout 
# or use http.socket.timeout in httpclient.parameters
# Value is in milliseconds
#httpclient.timeout=0
# 0 == no timeout

# Set the http version (defaults to 1.1)
#httpclient.version=1.0 (or use the parameter http.protocol.version)

# Define characters per second > 0 to emulate slow connections
#httpclient.socket.http.cps=0
#httpclient.socket.https.cps=0

#Enable loopback protocol
#httpclient.loopback=true

# Define the local host address to be used for multi-homed hosts
#httpclient.localaddress=1.2.3.4

# AuthManager Kerberos configuration
# Name of application module used in jaas.conf
#kerberos_jaas_application=JMeter  

# Should ports be stripped from urls before constructing SPNs
# for spnego authentication
#kerberos.spnego.strip_port=true

#         Sample logging levels for Commons HttpClient
#
# Commons HttpClient Logging information can be found at:
# http://hc.apache.org/httpclient-3.x/logging.html

# Note that full category names are used, i.e. must include the org.apache.
# Info level produces no output:
#log_level.org.apache.commons.httpclient=debug
# Might be useful:
#log_level.org.apache.commons.httpclient.Authenticator=trace 

# Show headers only
#log_level.httpclient.wire.header=debug

# Full wire debug produces a lot of output; consider using separate file:
#log_level.httpclient.wire=debug
#log_file.httpclient=httpclient.log


#         Apache Commons HttpClient logging examples
#
# Enable header wire + context logging - Best for Debugging
#log_level.org.apache.http=DEBUG
#log_level.org.apache.http.wire=ERROR

# Enable full wire + context logging
#log_level.org.apache.http=DEBUG

# Enable context logging for connection management
#log_level.org.apache.http.impl.conn=DEBUG

# Enable context logging for connection management / request execution
#log_level.org.apache.http.impl.conn=DEBUG
#log_level.org.apache.http.impl.client=DEBUG
#log_level.org.apache.http.client=DEBUG

#---------------------------------------------------------------------------
# Apache HttpComponents HTTPClient configuration (HTTPClient4)
#---------------------------------------------------------------------------

# Number of retries to attempt (default 0)
#httpclient4.retrycount=0

# Idle connection timeout (ms) to apply if the server does not send Keep-Alive headers
#httpclient4.idletimeout=0
# Note: this is currently an experimental fix

#---------------------------------------------------------------------------
# Apache HttpComponents HTTPClient configuration (HTTPClient 3.1)
#---------------------------------------------------------------------------

# Number of retries to attempt (default 0)
#httpclient3.retrycount=0

#---------------------------------------------------------------------------
# HTTP Cache Manager configuration
#---------------------------------------------------------------------------
#
# Space or comma separated list of methods that can be cached
#cacheable_methods=GET
# N.B. This property is currently a temporary solution for Bug 56162

# Since 2.12, JMeter does not create anymore a Sample Result with 204 response 
# code for a resource found in cache which is inline with what browser do.
#cache_manager.cached_resource_mode=RETURN_NO_SAMPLE

# You can choose between 3 modes:
# RETURN_NO_SAMPLE (default)
# RETURN_200_CACHE
# RETURN_CUSTOM_STATUS

# Those mode have the following behaviours:
# RETURN_NO_SAMPLE : this mode returns no Sample Result, it has no additional configuration
# RETURN_200_CACHE : this mode will return Sample Result with response code to 200 and response message to "(ex cache)", you can modify response message by setting 
# RETURN_200_CACHE.message=(ex cache)
# RETURN_CUSTOM_STATUS : This mode lets you select what response code and message you want to return, if you use this mode you need to set those properties
# RETURN_CUSTOM_STATUS.code=
# RETURN_CUSTOM_STATUS.message=

#---------------------------------------------------------------------------
# Results file configuration
#---------------------------------------------------------------------------

# This section helps determine how result data will be saved.
# The commented out values are the defaults.

# legitimate values: xml, csv, db.  Only xml and csv are currently supported.
jmeter.save.saveservice.output_format=csv


# true when field should be saved; false otherwise

 assertion_results_failure_message only affects CSV output
jmeter.save.saveservice.assertion_results_failure_message=false
#
# legitimate values: none, first, all
jmeter.save.saveservice.assertion_results=none
#
jmeter.save.saveservice.data_type=true
jmeter.save.saveservice.label=true
jmeter.save.saveservice.response_code=true
# response_data is not currently supported for CSV output
jmeter.save.saveservice.response_data=false
# Save ResponseData for failed samples
jmeter.save.saveservice.response_data.on_error=true
jmeter.save.saveservice.response_message=true
jmeter.save.saveservice.successful=true
jmeter.save.saveservice.thread_name=true
#jmeter.save.saveservice.time=true
jmeter.save.saveservice.subresults=true
jmeter.save.saveservice.assertions=true
jmeter.save.saveservice.latency=true
jmeter.save.saveservice.connect_time=true
jmeter.save.saveservice.samplerData=true
jmeter.save.saveservice.responseHeaders=true
jmeter.save.saveservice.requestHeaders=true
jmeter.save.saveservice.encoding=true
jmeter.save.saveservice.bytes=true
jmeter.save.saveservice.url=true
jmeter.save.saveservice.filename=true
jmeter.save.saveservice.hostname=true
jmeter.save.saveservice.thread_counts=true
jmeter.save.saveservice.sample_count=true
jmeter.save.saveservice.idle_time=true

# Timestamp format - this only affects CSV output files
# legitimate values: none, ms, or a format suitable for SimpleDateFormat
jmeter.save.saveservice.timestamp_format=ms
jmeter.save.saveservice.timestamp_format=yyyy/MM/dd HH:mm:ss.SSS

# For use with Comma-separated value (CSV) files or other formats
# where the fields' values are separated by specified delimiters.
# Default:
#jmeter.save.saveservice.default_delimiter=,
# For TAB, since JMeter 2.3 one can use:
#jmeter.save.saveservice.default_delimiter=\t

# Only applies to CSV format files:
jmeter.save.saveservice.print_field_names=true

# Optional list of JMeter variable names whose values are to be saved in the result data files.
# Use commas to separate the names. For example:
#sample_variables=SESSION_ID,REFERENCE
# N.B. The current implementation saves the values in XML as attributes,
# so the names must be valid XML names.
# Versions of JMeter after 2.3.2 send the variable to all servers
# to ensure that the correct data is available at the client.

# Optional xml processing instruction for line 2 of the file:
#jmeter.save.saveservice.xml_pi=<?xml-stylesheet type="text/xsl" href="../extras/jmeter-results-detail-report_21.xsl"?>

# Prefix used to identify filenames that are relative to the current base
#jmeter.save.saveservice.base_prefix=~/

# AutoFlush on each line written in XML or CSV output
# Setting this to true will result in less test results data loss in case of Crash
# but with impact on performances, particularly for intensive tests (low or no pauses)
# Since JMeter 2.10, this is false by default
jmeter.save.saveservice.autoflush=true

#---------------------------------------------------------------------------
# Settings that affect SampleResults
#---------------------------------------------------------------------------

# Save the start time stamp instead of the end
# This also affects the timestamp stored in result files
sampleresult.timestamp.start=true

# Whether to use System.nanoTime() - otherwise only use System.currentTimeMillis()
#sampleresult.useNanoTime=true

# Use a background thread to calculate the nanoTime offset
# Set this to <= 0 to disable the background thread
#sampleresult.nanoThreadSleep=5000

#---------------------------------------------------------------------------
# Upgrade property
#---------------------------------------------------------------------------

# File that holds a record of name changes for backward compatibility issues
upgrade_properties=/bin/upgrade.properties

#---------------------------------------------------------------------------
# JMeter Test Script recorder configuration
#
# N.B. The element was originally called the Proxy recorder, which is why the
# properties have the prefix "proxy".
#---------------------------------------------------------------------------

# If the recorder detects a gap of at least 5s (default) between HTTP requests,
# it assumes that the user has clicked a new URL
#proxy.pause=5000

# Add numeric prefix to Sampler names (default true)
#proxy.number.requests=true

# List of URL patterns that will be added to URL Patterns to exclude
# Separate multiple lines with ;
#proxy.excludes.suggested=.*\\.(bmp|css|js|gif|ico|jpe?g|png|swf|woff)

# Change the default HTTP Sampler (currently HttpClient4)
# Java:
#jmeter.httpsampler=HTTPSampler
#or
#jmeter.httpsampler=Java
#
# Apache HTTPClient:
#jmeter.httpsampler=HTTPSampler2
#or
#jmeter.httpsampler=HttpClient3.1
#
# HttpClient4.x
#jmeter.httpsampler=HttpClient4

# By default JMeter tries to be more lenient with RFC2616 redirects and allows
# relative paths.
# If you want to test strict conformance, set this value to true
# When the property is true, JMeter follows http://tools.ietf.org/html/rfc3986#section-5.2
#jmeter.httpclient.strict_rfc2616=false

# Default content-type include filter to use
#proxy.content_type_include=text/html|text/plain|text/xml
# Default content-type exclude filter to use
#proxy.content_type_exclude=image/.*|text/css|application/.*

# Default headers to remove from Header Manager elements
# (Cookie and Authorization are always removed)
#proxy.headers.remove=If-Modified-Since,If-None-Match,Host

# Binary content-type handling
# These content-types will be handled by saving the request in a file:
#proxy.binary.types=application/x-amf,application/x-java-serialized-object
# The files will be saved in this directory:
#proxy.binary.directory=user.dir
# The files will be created with this file filesuffix:
#proxy.binary.filesuffix=.binary

#---------------------------------------------------------------------------
# Test Script Recorder certificate configuration
#---------------------------------------------------------------------------

#proxy.cert.directory=<JMeter bin directory>
#proxy.cert.file=proxyserver.jks
#proxy.cert.type=JKS
#proxy.cert.keystorepass=password
#proxy.cert.keypassword=password
#proxy.cert.factory=SunX509
# define this property if you wish to use your own keystore
#proxy.cert.alias=<none>
# The default validity for certificates created by JMeter
#proxy.cert.validity=7
# Use dynamic key generation (if supported by JMeter/JVM)
# If false, will revert to using a single key with no certificate
#proxy.cert.dynamic_keys=true

#---------------------------------------------------------------------------
# Test Script Recorder miscellaneous configuration
#---------------------------------------------------------------------------

# Whether to attempt disabling of samples that resulted from redirects
# where the generated samples use auto-redirection
#proxy.redirect.disabling=true

# SSL configuration
#proxy.ssl.protocol=TLS

#---------------------------------------------------------------------------
# JMeter Proxy configuration
#---------------------------------------------------------------------------
# use command-line flags for user-name and password
#http.proxyDomain=NTLM domain, if required by HTTPClient sampler

#---------------------------------------------------------------------------
# HTTPSampleResponse Parser configuration
#---------------------------------------------------------------------------

# Space-separated list of parser groups
HTTPResponse.parsers=htmlParser wmlParser
# for each parser, there should be a parser.types and a parser.className property

#---------------------------------------------------------------------------
# HTML Parser configuration
#---------------------------------------------------------------------------

# Define the HTML parser to be used.
# Default parser:
# This new parser (since 2.10) should perform better than all others
# see https://issues.apache.org/bugzilla/show_bug.cgi?id=55632
#htmlParser.className=org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser

# Other parsers:
# Default parser before 2.10
#htmlParser.className=org.apache.jmeter.protocol.http.parser.HtmlParserHTMLParser
#htmlParser.className=org.apache.jmeter.protocol.http.parser.JTidyHTMLParser
# Note that Regexp extractor may detect references that have been commented out.
# In many cases it will work OK, but you should be aware that it may generate 
# additional references.
#htmlParser.className=org.apache.jmeter.protocol.http.parser.RegexpHTMLParser
# This parser is based on JSoup, it should be the most accurate but less performant
# than LagartoBasedHtmlParser
#htmlParser.className=org.apache.jmeter.protocol.http.parser.JsoupBasedHtmlParser

#Used by HTTPSamplerBase to associate htmlParser with content types below 
htmlParser.types=text/html application/xhtml+xml application/xml text/xml

#---------------------------------------------------------------------------
# WML Parser configuration
#---------------------------------------------------------------------------

wmlParser.className=org.apache.jmeter.protocol.http.parser.RegexpHTMLParser

#Used by HTTPSamplerBase to associate wmlParser with content types below 
wmlParser.types=text/vnd.wap.wml 

#---------------------------------------------------------------------------
# Remote batching configuration
#---------------------------------------------------------------------------
# How is Sample sender implementations configured:
# - true (default) means client configuration will be used
# - false means server configuration will be used
#sample_sender_client_configured=true

# Remote batching support
# Since JMeter 2.9, default is MODE_STRIPPED_BATCH, which returns samples in
# batch mode (every 100 samples or every minute by default)
# Note also that MODE_STRIPPED_BATCH strips response data from SampleResult, so if you need it change to
# another mode
# Hold retains samples until end of test (may need lots of memory)
# Batch returns samples in batches
# Statistical returns sample summary statistics
# hold_samples was originally defined as a separate property,
# but can now also be defined using mode=Hold
# mode can also be the class name of an implementation of org.apache.jmeter.samplers.SampleSender
#mode=Standard
#mode=Batch
#mode=Hold
#mode=Statistical
#Set to true to key statistical samples on threadName rather than threadGroup
#key_on_threadname=false
#mode=Stripped
#mode=StrippedBatch
#mode=org.example.load.MySampleSender
#
#num_sample_threshold=100
# Value is in milliseconds
#time_threshold=60000
#
# Asynchronous sender; uses a queue and background worker process to return the samples
#mode=Asynch
# default queue size
#asynch.batch.queue.size=100
# Same as Asynch but strips response data from SampleResult
#mode=StrippedAsynch
#
# DiskStore: as for Hold mode, but serialises the samples to disk, rather than saving in memory
#mode=DiskStore
# Same as DiskStore but strips response data from SampleResult
#mode=StrippedDiskStore
# Note: the mode is currently resolved on the client; 
# other properties (e.g. time_threshold) are resolved on the server.

# To set the Monitor Health Visualiser buffer size, enter the desired value
# monitor.buffer.size=800

#---------------------------------------------------------------------------
# JDBC Request configuration
#---------------------------------------------------------------------------

# Max number of PreparedStatements per Connection for PreparedStatement cache
#jdbcsampler.maxopenpreparedstatements=100

# String used to indicate a null value
#jdbcsampler.nullmarker=]NULL[

#---------------------------------------------------------------------------
# OS Process Sampler configuration
#---------------------------------------------------------------------------
# Polling to see if process has finished its work, used when a timeout is configured on sampler
#os_sampler.poll_for_timeout=100

#---------------------------------------------------------------------------
# TCP Sampler configuration
#---------------------------------------------------------------------------

# The default handler class
#tcp.handler=TCPClientImpl
#
# eolByte = byte value for end of line
# set this to a value outside the range -128 to +127 to skip eol checking
#tcp.eolByte=1000
#
# TCP Charset, used by org.apache.jmeter.protocol.tcp.sampler.TCPClientImpl
# default to Platform defaults charset as returned by Charset.defaultCharset().name()
#tcp.charset=
#
# status.prefix and suffix = strings that enclose the status response code
#tcp.status.prefix=Status=
#tcp.status.suffix=.
#
# status.properties = property file to convert codes to messages
#tcp.status.properties=mytestfiles/tcpstatus.properties

# The length prefix used by LengthPrefixedBinaryTCPClientImpl implementation
# defaults to 2 bytes.
#tcp.binarylength.prefix.length=2

#---------------------------------------------------------------------------
# Summariser - Generate Summary Results - configuration (mainly applies to non-GUI mode)
#---------------------------------------------------------------------------
#
# Define the following property to automatically start a summariser with that name
# (applies to non-GUI mode only)
#summariser.name=summary
#
# interval between summaries (in seconds) default 30 seconds
#summariser.interval=30
#
# Write messages to log file
#summariser.log=true
#
# Write messages to System.out
#summariser.out=true


#---------------------------------------------------------------------------
# Aggregate Report and Aggregate Graph - configuration
#---------------------------------------------------------------------------
#
# Percentiles to display in reports
# Can be float value between 0 and 100
# First percentile to display, defaults to 90%
#aggregate_rpt_pct1=90
# Second percentile to display, defaults to 95%
#aggregate_rpt_pct2=95
# Second percentile to display, defaults to 99%
#aggregate_rpt_pct3=99

#---------------------------------------------------------------------------
# Aggregate Report and Aggregate Graph - configuration
#---------------------------------------------------------------------------
#
# Backend metrics sliding window size for Percentiles, Min, Max
#backend_metrics_window=100

#---------------------------------------------------------------------------
# BeanShell configuration
#---------------------------------------------------------------------------

# BeanShell Server properties
#
# Define the port number as non-zero to start the http server on that port
#beanshell.server.port=9000
# The telnet server will be started on the next port

#
# Define the server initialisation file
beanshell.server.file=../extras/startup.bsh

#
# Define a file to be processed at startup
# This is processed using its own interpreter.
#beanshell.init.file=

#
# Define the intialisation files for BeanShell Sampler, Function and other BeanShell elements
# N.B. Beanshell test elements do not share interpreters.
#      Each element in each thread has its own interpreter.
#      This is retained between samples.
#beanshell.sampler.init=BeanShellSampler.bshrc
#beanshell.function.init=BeanShellFunction.bshrc
#beanshell.assertion.init=BeanShellAssertion.bshrc
#beanshell.listener.init=etc
#beanshell.postprocessor.init=etc
#beanshell.preprocessor.init=etc
#beanshell.timer.init=etc

# The file BeanShellListeners.bshrc contains sample definitions
# of Test and Thread Listeners.

#---------------------------------------------------------------------------
# MailerModel configuration
#---------------------------------------------------------------------------

# Number of successful samples before a message is sent
#mailer.successlimit=2
#
# Number of failed samples before a message is sent
#mailer.failurelimit=2

#---------------------------------------------------------------------------
# CSVRead configuration
#---------------------------------------------------------------------------

# CSVRead delimiter setting (default ",")
# Make sure that there are no trailing spaces or tabs after the delimiter
# characters, or these will be included in the list of valid delimiters
#csvread.delimiter=,
#csvread.delimiter=;
#csvread.delimiter=!
#csvread.delimiter=~
# The following line has a tab after the =
#csvread.delimiter=	

#---------------------------------------------------------------------------
# __time() function configuration
#
# The properties below can be used to redefine the default formats
#---------------------------------------------------------------------------
#time.YMD=yyyyMMdd
#time.HMS=HHmmss
#time.YMDHMS=yyyyMMdd-HHmmss
#time.USER1=
#time.USER2=

#---------------------------------------------------------------------------
# CSV DataSet configuration
#---------------------------------------------------------------------------

# String to return at EOF (if recycle not used)
#csvdataset.eofstring=<EOF>

#---------------------------------------------------------------------------
# LDAP Sampler configuration
#---------------------------------------------------------------------------
# Maximum number of search results returned by a search that will be sorted
# to guarantee a stable ordering (if more results then this limit are retruned
# then no sorting is done). Set to 0 to turn off all sorting, in which case
# "Equals" response assertions will be very likely to fail against search results.
#
#ldapsampler.max_sorted_results=1000
 
# Number of characters to log for each of three sections (starting matching section, diff section,
#   ending matching section where not all sections will appear for all diffs) diff display when an Equals
#   assertion fails. So a value of 100 means a maximum of 300 characters of diff text will be displayed
#   (+ a number of extra characters like "..." and "[[["/"]]]" which are used to decorate it).
#assertion.equals_section_diff_len=100
# test written out to log to signify start/end of diff delta
#assertion.equals_diff_delta_start=[[[
#assertion.equals_diff_delta_end=]]]

#---------------------------------------------------------------------------
# Miscellaneous configuration
#---------------------------------------------------------------------------

# If defined, then start the mirror server on the port
#mirror.server.port=8081

# ORO PatternCacheLRU size
#oro.patterncache.size=1000

#TestBeanGui
#
#propertyEditorSearchPath=null

# Turn expert mode on/off: expert mode will show expert-mode beans and properties
#jmeter.expertMode=true

# Maximum redirects to follow in a single sequence (default 5)
#httpsampler.max_redirects=5
# Maximum frame/iframe nesting depth (default 5)
#httpsampler.max_frame_depth=5
# Maximum await termination timeout (secs) when concurrent download embedded resources (default 60)
#httpsampler.await_termination_timeout=60
# Revert to BUG 51939 behaviour (no separate container for embedded resources) by setting the following false:
#httpsampler.separate.container=true

# If embedded resources download fails due to missing resources or other reasons, if this property is true
# Parent sample will not be marked as failed 
#httpsampler.ignore_failed_embedded_resources=false

# The encoding to be used if none is provided (default ISO-8859-1)
#sampleresult.default.encoding=ISO-8859-1

# Network response size calculation method
# Use real size: number of bytes for response body return by webserver
# (i.e. the network bytes received for response)
# if set to false, the (uncompressed) response data size will used (default before 2.5)
# Include headers: add the headers size in real size
#sampleresult.getbytes.body_real_size=true
#sampleresult.getbytes.headers_size=true

# CookieManager behaviour - should cookies with null/empty values be deleted?
# Default is true. Use false to revert to original behaviour
#CookieManager.delete_null_cookies=true

# CookieManager behaviour - should variable cookies be allowed?
# Default is true. Use false to revert to original behaviour
#CookieManager.allow_variable_cookies=true

# CookieManager behaviour - should Cookies be stored as variables?
# Default is false
#CookieManager.save.cookies=false

# CookieManager behaviour - prefix to add to cookie name before storing it as a variable
# Default is COOKIE_; to remove the prefix, define it as one or more spaces
#CookieManager.name.prefix=
 
# CookieManager behaviour - check received cookies are valid before storing them?
# Default is true. Use false to revert to previous behaviour
#CookieManager.check.cookies=true

# (2.0.3) JMeterThread behaviour has been changed to set the started flag before
# the controllers are initialised. This is so controllers can access variables earlier. 
# In case this causes problems, the previous behaviour can be restored by uncommenting
# the following line.
#jmeterthread.startearlier=false

# (2.2.1) JMeterThread behaviour has changed so that PostProcessors are run in forward order
# (as they appear in the test plan) rather than reverse order as previously.
# Uncomment the following line to revert to the original behaviour
#jmeterthread.reversePostProcessors=true

# (2.2) StandardJMeterEngine behaviour has been changed to notify the listeners after
# the running version is enabled. This is so they can access variables. 
# In case this causes problems, the previous behaviour can be restored by uncommenting
# the following line.
#jmeterengine.startlistenerslater=false

# Number of milliseconds to wait for a thread to stop
#jmeterengine.threadstop.wait=5000

#Whether to invoke System.exit(0) in server exit code after stopping RMI
#jmeterengine.remote.system.exit=false

# Whether to call System.exit(1) on failure to stop threads in non-GUI mode.
# This only takes effect if the test was explictly requested to stop.
# If this is disabled, it may be necessary to kill the JVM externally
#jmeterengine.stopfail.system.exit=true

# Whether to force call System.exit(0) at end of test in non-GUI mode, even if
# there were no failures and the test was not explicitly asked to stop.
# Without this, the JVM may never exit if there are other threads spawned by
# the test which never exit.
#jmeterengine.force.system.exit=false

# How long to pause (in ms) in the daemon thread before reporting that the JVM has failed to exit.
# If the value is <= 0, the JMeter does not start the daemon thread 
#jmeter.exit.check.pause=2000

# If running non-GUI, then JMeter listens on the following port for a shutdown message.
# To disable, set the port to 1000 or less.
#jmeterengine.nongui.port=4445
#
# If the initial port is busy, keep trying until this port is reached
# (to disable searching, set the value less than or equal to the .port property)
#jmeterengine.nongui.maxport=4455

# How often to check for shutdown during ramp-up (milliseconds)
#jmeterthread.rampup.granularity=1000

#Should JMeter expand the tree when loading a test plan?
# default value is false since JMeter 2.7
#onload.expandtree=false

#JSyntaxTextArea configuration
#jsyntaxtextarea.wrapstyleword=true
#jsyntaxtextarea.linewrap=true
#jsyntaxtextarea.codefolding=true
# Set 0 to disable undo feature in JSyntaxTextArea
#jsyntaxtextarea.maxundos=50

# Set this to false to disable the use of JSyntaxTextArea for the Console Logger panel 
#loggerpanel.usejsyntaxtext=true

# Maximum size of HTML page that can be displayed; default=200 * 1024
# Set to 0 to disable the size check and display the whole response
#view.results.tree.max_size=204800

# Order of Renderers in View Results Tree
# Note full class names should be used for non jmeter core renderers
# For JMeter core renderers, class names start with . and are automatically
# prefixed with org.apache.jmeter.visualizers
view.results.tree.renderers_order=.RenderAsText,.RenderAsRegexp,.RenderAsCssJQuery,.RenderAsXPath,.RenderAsHTML,.RenderAsHTMLWithEmbedded,.RenderAsDocument,.RenderAsJSON,.RenderAsXML

# Maximum size of Document that can be parsed by Tika engine; defaut=10 * 1024 * 1024 (10MB)
# Set to 0 to disable the size check
#document.max_size=0

#JMS options
# Enable the following property to stop JMS Point-to-Point Sampler from using
# the properties java.naming.security.[principal|credentials] when creating the queue connection
#JMSSampler.useSecurity.properties=false

# Set the following value to true in order to skip the delete confirmation dialogue
#confirm.delete.skip=false

# Used by Webservice Sampler (SOAP)
# Size of Document Cache
#soap.document_cache=50

# Used by JSR223 elements
# Size of compiled scripts cache
#jsr223.compiled_scripts_cache_size=100

#---------------------------------------------------------------------------
# Classpath configuration
#---------------------------------------------------------------------------

# List of paths (separated by ;) to search for additional JMeter plugin classes,
# for example new GUI elements and samplers.
# A path item can either be a jar file or a directory.
# Any jar file in such a directory will be automatically included,
# jar files in sub directories are ignored.
# The given value is in addition to any jars found in the lib/ext directory.
# Do not use this for utility or plugin dependency jars.
#search_paths=/app1/lib;/app2/lib

# List of paths that JMeter will search for utility and plugin dependency classes.
# Use your platform path separator to separate multiple paths.
# A path item can either be a jar file or a directory.
# Any jar file in such a directory will be automatically included,
# jar files in sub directories are ignored.
# The given value is in addition to any jars found in the lib directory.
# All entries will be added to the class path of the system class loader
# and also to the path of the JMeter internal loader.
# Paths with spaces may cause problems for the JVM
#user.classpath=../classes;../lib;../app1/jar1.jar;../app2/jar2.jar

# List of paths (separated by ;) that JMeter will search for utility
# and plugin dependency classes.
# A path item can either be a jar file or a directory.
# Any jar file in such a directory will be automatically included,
# jar files in sub directories are ignored.
# The given value is in addition to any jars found in the lib directory
# or given by the user.classpath property.
# All entries will be added to the path of the JMeter internal loader only.
# For plugin dependencies using plugin_dependency_paths should be preferred over
# user.classpath.
#plugin_dependency_paths=../dependencies/lib;../app1/jar1.jar;../app2/jar2.jar

# Classpath finder
# ================
# The classpath finder currently needs to load every single JMeter class to find
# the classes it needs.
# For non-GUI mode, it's only necessary to scan for Function classes, but all classes
# are still loaded.
# All current Function classes include ".function." in their name,
# and none include ".gui." in the name, so the number of unwanted classes loaded can be
# reduced by checking for these. However, if a valid function class name does not match
# these restrictions, it will not be loaded. If problems are encountered, then comment
# or change the following properties:
classfinder.functions.contain=.functions.
classfinder.functions.notContain=.gui.

#---------------------------------------------------------------------------
# Additional property files to load
#---------------------------------------------------------------------------

# Should JMeter automatically load additional JMeter properties?
# File name to look for (comment to disable)
user.properties=user.properties

# Should JMeter automatically load additional system properties?
# File name to look for (comment to disable)
system.properties=system.properties

# Comma separated list of files that contain reference to templates and their description
# Path must be relative to jmeter root folder
#template.files=/bin/templates/templates.xml

[Dmitri Tikhanski]

Revert your changes, results file I mentioned can be obtained using default settings.

Just run JMeter in command-line non-GUI mode as

jmeter -n -t /path/to/your-script.jmx -l /path/to/test-results.jtl

This test-results.jtl file will be in CSV format and will contain response code and response message along with other metrics as per my above example.

[Angus Ferguson]

I would like to schedule the start of it, no do it manually

Any idea, please?

[Angus Ferguson]

also when I scheduled my tests they doesnt start automatically all looks correct for me the startup delay option is 0.

Any idea, please?

[Angus Ferguson]

You don't need to re-invent the wheel, JMeter automatically saves response message in its .jtl results file.

Yes but what I want is something like this:

When error 500 happens then: The person in charge of the app should restart the server...
When error XXX happens then: The person in charge of the app should do the appropiate action

and so on thats why looks like I need to use a script like this isnt it?

FileOutputStream out = new FileOutputStream(sugarTrendsLoadTest, true);
String newline = System.getProperty("line.separator");
int code = Integer.parseInt(ResponseCode);
switch (code) {
  case 200:
      out.write("Response code is 200".getBytes());
      out.write(newline.getBytes());
      out.write("Working fine");
      break;
  case 500:
      out.write("Response code is 500".getBytes());
      out.write("Internal server error. Contact your server provider or check your server manually");
      break;
  default:
      break;
 
}

In order write the customized message for every code

[Angus Ferguson]

when I use

Isaacs-Mac-mini:bin isaac$ jmeter -n -t SugarTrendstarde.jmx -l test-results.jtl
-bash: jmeter: command not found

or this

Isaacs-Mac-mini:bin isaac$ ./jmeter -n -t SugarTrendstarde.jmx -l jmeteroutput.csv
-bash: ./jmeter: Permission denied

Any idea?

[Dmitri Tikhanski]

If you need a custom message for each response code - you'll have to use a script.

For JMeter execution problem - try adding execution permissions to jmeter binary as:

chmod +x jmeter

To schedule JMeter execution on MacOSX see How can I get a script to run every day on Mac OS X?

For other JMeter execution options (other than command-line) check out Five Ways To Launch a JMeter Test without Using the JMeter GUI guide.

[Angus Ferguson]

Now I get this one:

Isaacs-Mac-mini:~ isaac$ chmod +x jmeter -n -t SugarTrendstarde.jmx -l test-results.jtl 
chmod: jmeter: No such file or directory
chmod: -n: No such file or directory
chmod: -t: No such file or directory
chmod: SugarTrendstarde.jmx: No such file or directory
chmod: -l: No such file or directory
chmod: test-results.jtl: No such file or directory

Any idea, please?

[Dmitri Tikhanski]

1. Go to JMeter /bin folder
2. Execute "chmod +x jmeter"
3. Make sure that you can launch JMeter GUI by "./jmeter" command
4. Close the GUI
5. Execute "jmeter -n -t ...." command

[Angus Ferguson]

I made all the steps and the last one after close the GUI shows this error:

Isaacs-Mac-mini:bin isaac$ jmeter -n -t Sugartarde.jmx -l test-results.jtl 
-bash: jmeter: command not found

I also tried it like this:

Isaacs-Mac-mini:bin isaac$ ./jmeter.sh -n -t Sugarstarde.jmx -l test-results.jtl 
-bash: ./jmeter.sh: Permission denied

How could I open a jtl?

Any idea, please?

[Dmitri Tikhanski]

Maybe it is a problem with your JMeter installation. The easiest way to get it installed on Mac is using Homebrew

Install Homebrew as

ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"

Install JMeter as

brew install jmeter

Run JMeter as

jmeter -n -t /path/to/your/script.jmx -l /path/to/resultsfile.jtl

Open JMeter GUI as

jmeter

Add Listener of your choice to the test plan, using Browse button locate .jtl file and open it.

Analyze results.

Maybe it will be easier for you to use Taurus tool instead, it simplifies many JMeter aspects.

[Angus Ferguson]

Well I got the jtl file. Maybe this question is out of context, or not extrictly about programming. As I never have analized a jtl file, or any result coming from JMeter. Could I find posible bottlenecks in the code, or performance problems in the server, in other words how could I get conclusions about the web application behaviour and know to improve it? I mean how could I interpret the result I have got from JMeter?

Also if I in JMeter use 500 number of threads and a ranp up period of 100. Does it mean that 5 users per second are added to the execution of the test? So second 1: 5 users, second 2: 10 users .....second 100: 500 users are active using the site concurrently at the same time?

To schedule JMeter execution on MacOSX see How can I get a script to run every day on Mac OS X?

Any idea, please?

[Dmitri Tikhanski]

For better results representation I once again recommend running your .jmx file using Taurus tool, this way you'll be able to get easy-understandable graph reports.

For ramp-up: if you have enough loops - the answer is yes. JMeter starts with 0 threads and add threads each second as per your ramp-up scenario. In your case it will be 5 users each second. On start threads begin executing samplers upside down (or according to the Logic Controllers). When thread doesn't have any more samplers to execute and loops to iterate it's being shut down. So make sure you provide enough loops to achieve desired concurrency. Alternatively you can put loop number to "Forever" and set desired test duration under "Scheduler" section in the Thread Group

Schedule execution on Mac -

1. iCal alarm with "Run Script" action
2. launchd

[Angus Ferguson]

I recorded a scenario with 5000 users and a ramp up of 100. The result shows a failure after 20 seconds and then it recovers it works for a while and then it fails again like this:

2015/09/23 00:06:47.863,4134,RequestAbouUs,200,OK,Dopmain 1-22,text,true,1526139,103,103,https://www.mydomain.com/,,673,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,160
2015/09/23 00:06:47.516,4474,RequestAbouUs,200,OK,Dopmain 1-21,text,true,1526139,103,103,https://www.mydomain.com/,,1915,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,503
2015/09/23 00:06:47.998,4223,RequestAbouUs,200,OK,Dopmain 1-28,text,true,1526139,105,105,https://www.mydomain.com/,,1855,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,153
2015/09/23 00:06:47.180,5253,RequestAbouUs,200,OK,Dopmain 1-1,text,true,1526139,108,108,https://www.mydomain.com/,,2300,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,821
2015/09/23 00:06:48.239,4953,RequestAbouUs,200,OK,Dopmain 1-34,text,true,1526139,115,115,https://www.mydomain.com/,,2599,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,225
2015/09/23 00:06:47.217,6037,RequestAbouUs,200,OK,Dopmain 1-15,text,true,1526139,115,115,https://www.mydomain.com/,,4159,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,808
2015/09/23 00:06:48.116,6055,RequestAbouUs,200,OK,Dopmain 1-31,text,true,1526139,128,128,https://www.mydomain.com/,,2240,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,105
2015/09/23 00:06:48.454,13016,RequestAbouUs,200,OK,Dopmain 1-38,text,true,1526139,192,192,https://www.mydomain.com/,,4489,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,971
2015/09/23 00:06:48.810,16826,RequestAbouUs,200,OK,Dopmain 1-44,text,true,1526139,201,204,https://www.mydomain.com/,,4579,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,731
2015/09/23 00:06:47.177,15463,RequestAbouUs,200,OK,Dopmain 1-9,text,true,1526139,200,200,https://www.mydomain.com/,,5321,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,975
2015/09/23 00:06:47.443,19604,RequestAbouUs,200,OK,Dopmain 1-20,text,true,1526139,204,204,https://www.mydomain.com/,,4504,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,559
2015/09/23 00:06:47.854,26885,RequestAbouUs,200,OK,Dopmain 1-23,text,true,1526139,213,213,https://www.mydomain.com/,,8754,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,169
2015/09/23 00:06:50.025,21918,RequestAbouUs,200,OK,Dopmain 1-69,text,true,1526139,213,213,https://www.mydomain.com/,,6313,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,562
2015/09/23 00:06:47.304,21427,RequestAbouUs,200,OK,Dopmain 1-16,text,true,1526139,210,210,https://www.mydomain.com/,,6557,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,879
2015/09/23 00:07:07.044,466046,1 /,Non HTTP response code: java.net.SocketException,Non HTTP response message: Connection reset,SugarTrends 1-38,text,false,2435,183,183,https://www.mydomain.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:07:07.070,465984,1 /,Non HTTP response code: java.net.SocketException,Non HTTP response message: Connection reset,SugarTrends 1-44,text,false,2435,193,193,https://www.mydomain.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:07:07.093,462174,1 /,Non HTTP response code: org.apache.commons.httpclient.NoHttpResponseException,Non HTTP response message: The server www.sugartrends.com failed to respond,SugarTrends 1-20,text,false,1281,214,214,https://www.sugartrends.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:07:07.072,467290,1 /,Non HTTP response code: java.net.SocketException,Non HTTP response message: Connection reset,SugarTrends 1-9,text,false,2435,163,163,https://www.mydomain.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:07:08.617,467007,RequestAbouUs,Non HTTP response code: javax.net.ssl.SSLHandshakeException,Non HTTP response message: Remote host closed connection during handshake,Dopmain 1-202,text,false,2059,163,163,https://www.mydomain.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:07:08.613,466993,RequestAbouUs,Non HTTP response code: javax.net.ssl.SSLHandshakeException,Non HTTP response message: Remote host closed connection during handshake,Dopmain 1-203,text,false,2059,163,163,https://www.mydomain.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:07:07.314,469996,RequestAbouUs,Non HTTP response code: java.net.SocketException,Non HTTP response message: Connection reset,Dopmain 1-201,text,false,2578,142,142,https://www.mydomain.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:07:08.610,467003,RequestAbouUs,Non HTTP response code: javax.net.ssl.SSLHandshakeException,Non HTTP response message: Remote host closed connection during handshake,SugarTrends 1-204,text,false,2059,163,163,https://www.mydomain.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:07:08.612,467010,RequestAbouUs,Non HTTP response code: javax.net.ssl.SSLHandshakeException,Non HTTP response message: Remote host closed connection during handshake,SugarTrends 1-205,text,false,2059,163,163,https://www.mydomain.com/,,0,ISO-8859-1,1,1,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:14:54.303,13140,2 /media/css_secure/8dedc154dff6aa13bbb19cc03b95921e.css,200,OK,SugarTrends 1-38,text,true,17338,142,142,https://www.mydomain.com/media/css_secure/8dedc154dff6aa13bbb19cc03b95921e.css?q=1442913338,,13139,ISO-8859-1,1,0,Isaacs-Mac-mini.fritz.box,0,0
2015/09/23 00:06:49.274,499959,RequestAbouUs,200,OK,Dopmain 1-55,text,true,1526139,142,142,https://www.mydomain.com/,,7334,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,1439
2015/09/23 00:06:48.487,498833,RequestAbouUs,200,OK,Dopmain 1-40,text,true,1526139,142,142,https://www.mydomain.com/,,7986,UTF-8,1,0,Isaacs-Mac-mini.fritz.box,0,1344
2015/09/23 00:06:50.892,496558,RequestAbouUs,200,OK,Dopmain 1-85,text,false,1262071,142,142,https://www.Dopmain.com/,,7731,UTF-8,1,1,Isaacs-Mac-mini.fritz.box,0,

Any idea of what it can means? Should I increase the capabilities of the server? Should it be a bottleneck in the web app?

On the other hand also of the .jtl Im getting now in order to check if the server, the network, etc fails. Could I get without using the GUI(the test os for 5000 user and the terminal is recomended) get a file which contains reponse time, etc?

[Dmitri Tikhanski]

Again the question is out of scope of the original one. It is recommended to open a new thread for a different question.

It looks like you running into a situation described in Connection Reset since JMeter 2.10 ? wiki page.

If you're absolutely sure that everything is fine with your server, you can play with JMeter config to make these errors go away.

First of all, change "Implementation" of all your HTTP Request samplers to "HTTPClient4". The best way of doing it is HTTP Request Defaults

In user.properties file (in /bin folder of your JMeter installation) add next 2 lines:

httpclient4.retrycount=1
hc.parameters.file=hc.parameters

In hc.parameters file (again in JMeter's /bin folder) add (or uncomment and change the value for) the next line:

http.connection.stalecheck$Boolean=true

[Angus Ferguson]

Yes I should have deleted the previous one I found it on the net easily, I made it like in the link you posted and now I dont get that errors