Run jmeter distributed testing,all machines are gcp instances.Able to trigger tests from master to slaves.Problem is test results getting 100% Error rate 403/Forbidden. This happens on all the vms.I'm running a sample script with no external data files e.g csv,so it should be all pass. On running the tests on my local they pass just fine.
Master & slaves using same version of jmeter,java and plugins
server.log of one of the vms
2022-09-02 07:12:13,318 INFO o.a.j.e.RemoteJMeterEngineImpl: Running test
2022-09-02 07:12:13,330 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2022-09-02 07:12:13,330 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2022-09-02 07:12:13,356 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must contain the string: '.functions.'
2022-09-02 07:12:13,356 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must not contain the string: '.gui.'
2022-09-02 07:12:13,822 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Users
2022-09-02 07:12:13,822 INFO o.a.j.e.StandardJMeterEngine: Starting 10 threads for group Users.
2022-09-02 07:12:13,822 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2022-09-02 07:12:13,823 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=10 ramp-up=10 delayedStart=false
2022-09-02 07:12:13,851 INFO o.a.j.s.SampleResult: Note: Sample TimeStamps are START times
2022-09-02 07:12:13,851 INFO o.a.j.s.SampleResult: sampleresult.default.encoding is set to ISO-8859-1
2022-09-02 07:12:13,851 INFO o.a.j.s.SampleResult: sampleresult.useNanoTime=true
2022-09-02 07:12:13,851 INFO o.a.j.s.SampleResult: sampleresult.nanoThreadSleep=5000
2022-09-02 07:12:13,854 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-1
2022-09-02 07:12:13,912 INFO o.a.j.p.h.s.HTTPHCAbstractImpl: Local host = jmeter-worker-prf-002
2022-09-02 07:12:13,913 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2022-09-02 07:12:13,913 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2022-09-02 07:12:13,928 INFO o.a.j.p.h.s.HTTPHC4Impl: HTTP request retry count = 0
2022-09-02 07:12:14,024 INFO o.a.j.p.h.s.h.LazyLayeredConnectionSocketFactory: Setting up HTTPS TrustAll Socket Factory
2022-09-02 07:12:14,029 INFO o.a.j.u.JsseSSLManager: Using default SSL protocol: TLS
2022-09-02 07:12:14,029 INFO o.a.j.u.JsseSSLManager: SSL session context: per-thread
2022-09-02 07:12:14,034 INFO o.a.j.u.SSLManager: JmeterKeyStore Location: type JKS
2022-09-02 07:12:14,035 INFO o.a.j.u.SSLManager: KeyStore created OK
2022-09-02 07:12:14,035 WARN o.a.j.u.SSLManager: Keystore file not found, loading empty keystore
2022-09-02 07:12:14,504 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-1
2022-09-02 07:12:14,504 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-1
2022-09-02 07:12:14,852 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-2
2022-09-02 07:12:15,094 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-2
2022-09-02 07:12:15,094 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-2
2022-09-02 07:12:15,847 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-3
2022-09-02 07:12:16,076 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-3
2022-09-02 07:12:16,076 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-3
2022-09-02 07:12:16,840 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-4
2022-09-02 07:12:17,059 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-4
2022-09-02 07:12:17,059 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-4
2022-09-02 07:12:17,840 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-5
2022-09-02 07:12:18,063 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-5
2022-09-02 07:12:18,063 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-5
2022-09-02 07:12:18,831 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-6
2022-09-02 07:12:19,052 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-6
2022-09-02 07:12:19,052 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-6
2022-09-02 07:12:19,843 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-7
2022-09-02 07:12:20,076 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-7
2022-09-02 07:12:20,076 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-7
2022-09-02 07:12:20,829 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-8
2022-09-02 07:12:21,148 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-8
2022-09-02 07:12:21,148 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-8
2022-09-02 07:12:21,845 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-9
2022-09-02 07:12:22,052 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-9
2022-09-02 07:12:22,052 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-9
2022-09-02 07:12:22,841 INFO o.a.j.t.JMeterThread: Thread started: 10.10.52.197-Users 1-10
2022-09-02 07:12:23,092 INFO o.a.j.t.JMeterThread: Thread is done: 10.10.52.197-Users 1-10
2022-09-02 07:12:23,092 INFO o.a.j.t.JMeterThread: Thread finished: 10.10.52.197-Users 1-10
the only error i see is
2022-09-02 07:12:14,035 WARN o.a.j.u.SSLManager: Keystore file not
found, loading empty keystore
could that be the issue?though i didnt load any keystore on local
jmeter.log file doesn't tell the full story (at least until you enable debug logging)
First of all try temporarily enabling saving of request and response details for local and remote runs and compare resulting .jtl files. By default JMeter stores metrics in CSV format so you either need to amend Results File Configuration or add a Listener like Simple Data Writer and configure what and where to store
if the requests are the same enable debug logging and compare jmeter.log files. If there are no suspicious entries there try running your test from a machine on GCP in command-line non-GUI mode (not-distributed test run) as it might be the case your application doesn't allow incoming traffic from there
Related
while running all the tests at the same time, the tests take a long time to process and fail bad request.
If you run the same you individually, then everything is fine, the tests pass. What could be the problem, tell me please
https://prnt.sc/p4pagc
In logs writes it:
019-09-11 15:06:08,632 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2019-09-11 15:06:08,634 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2019-09-11 15:06:08,640 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, *local*)
2019-09-11 15:06:08,770 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : BILLING-API
2019-09-11 15:06:08,771 INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group BILLING-API.
2019-09-11 15:06:08,771 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2019-09-11 15:06:08,771 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=1 delayedStart=false
2019-09-11 15:06:08,772 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2019-09-11 15:06:08,773 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2019-09-11 15:06:08,789 INFO o.a.j.t.JMeterThread: Thread started: BILLING-API 1-1
2019-09-11 15:06:38,861 INFO o.a.j.t.JMeterThread: Thread is done: BILLING-API 1-1
2019-09-11 15:06:38,861 INFO o.a.j.t.JMeterThread: Thread finished: BILLING-API 1-1
2019-09-11 15:06:38,861 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2019-09-11 15:06:38,862 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, *local*)
In my test plan, I create a Thread Group configured as below:
1. Action to be taken after a Sampler error: Continue
2. Number of Threads(users):10000
3. Ramp-up Period(in seconds):1
4. Loop Count:1
5. Duration(seconds):2
6. Startup delay(seconds):10
There is an Http Request Sampler in Thread Group.
After run the test plan, in jmeter.log
2019-04-30 15:46:01,558 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group-WB
2019-04-30 15:46:01,558 INFO o.a.j.e.StandardJMeterEngine: Starting 10000 threads for group Thread Group-WB.
2019-04-30 15:46:01,558 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2019-04-30 15:46:01,559 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=10000 ramp-up=1 delayedStart=false
2019-04-30 15:46:06,549 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2019-04-30 15:46:06,549 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2019-04-30 15:46:11,559 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-1
2019-04-30 15:46:11,562 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-2
2019-04-30 15:46:11,614 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-67
...
2019-04-30 15:46:15,541 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-5884
2019-04-30 15:46:15,541 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-5890
2019-04-30 15:46:15,541 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-5891
...
2019-04-30 15:46:15,367 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-7239
...
2019-04-30 15:46:21,913 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group-WB 1-8506
2019-04-30 15:46:21,912 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group-WB 1-8505
...
2019-04-30 15:46:16,872 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-8042
2019-04-30 15:46:16,872 INFO o.a.j.t.JMeterThread: Thread started: Thread Group-WB 1-8041
2019-04-30 15:46:18,767 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group-WB 1-7239
2019-04-30 15:46:18,767 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group-WB 1-7239
2019-04-30 15:46:18,767 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group-WB 1-7239
...
2019-04-30 15:47:35,716 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group-WB 1-9783
2019-04-30 15:47:35,716 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group-WB 1-9783
2019-04-30 15:47:36,941 INFO o.a.j.t.JMeterThread: Stopping because end time detected by thread: Thread Group-WB 1-1037
2019-04-30 15:47:36,942 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group-WB 1-1037
2019-04-30 15:47:36,942 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group-WB 1-1037
2019-04-30 15:47:36,944 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2019-04-30 15:47:36,945 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, *local*)
The first Thread Group-wisebuy 1-1 start at 2019-04-30 15:46:11,559
I set Ramp-up Period as 1 second,why Thread Group-wisebuy 1-5891 started at 2019-04-30 15:46:15,541 ?
I set Duration as 2 seconds,why Thread Group-wisebuy 1-7239 stopping at 2019-04-30 15:46:18,767 ?
From the JMeter User's Manual:
The ramp-up period tells JMeter how long to take to "ramp-up" to the full number of threads chosen. If 10 threads are used, and the ramp-up period is 100 seconds, then JMeter will take 100 seconds to get all 10 threads up and running. Each thread will start 10 (100/10) seconds after the previous thread was begun.
By setting the ramp-up period to just 1 second, you're basically telling JMeter to start all 10,000 threads at once (i.e., as fast as it can).
Hence Thread 1-5891 started very soon after the first one. It looks like Thread 1-7239 started about 16s in, and therefore ended at around 18s because the duration = 2 seconds.
If you meant to start 1 user per second then you can set the ramp-up period = 1 second per # of users (10,000 seconds).
I'm trying to do JMeter testing in Mac and I have recorded a script in JMeter and when tried to playback the script, it doesn't run and gives the below error
2019-04-15 11:36:04,484 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2019-04-15 11:36:04,489 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2019-04-15 11:36:04,489 INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, *local*)
2019-04-15 11:36:04,690 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2019-04-15 11:36:04,690 INFO o.a.j.e.StandardJMeterEngine: Starting 5 threads for group Thread Group.
2019-04-15 11:36:04,690 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2019-04-15 11:36:04,691 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=5 ramp-up=1 delayedStart=false
2019-04-15 11:36:04,692 INFO o.a.j.t.ThreadGroup: Started thread group number 1
2019-04-15 11:36:04,691 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2019-04-15 11:36:04,692 INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
2019-04-15 11:36:04,692 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-1
2019-04-15 11:36:04,692 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-1
2019-04-15 11:36:04,895 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-2
2019-04-15 11:36:04,896 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-2
2019-04-15 11:36:04,896 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-2
2019-04-15 11:36:05,096 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-3
2019-04-15 11:36:05,097 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-3
2019-04-15 11:36:05,097 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-3
2019-04-15 11:36:05,294 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-4
2019-04-15 11:36:05,294 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-4
2019-04-15 11:36:05,294 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-4
2019-04-15 11:36:05,495 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-5
2019-04-15 11:36:05,496 INFO o.a.j.t.JMeterThread: Thread is done: Thread Group 1-5
2019-04-15 11:36:05,496 INFO o.a.j.t.JMeterThread: Thread finished: Thread Group 1-5
2019-04-15 11:36:05,496 INFO o.a.j.e.StandardJMeterEngine: Notifying test listeners of end of test
2019-04-15 11:36:05,496 INFO o.a.j.g.u.JMeterMenuBar: setRunning(false, *local*)
There is no error in your log.
Usually after recording, there is some correlation work to do.
First check you added a HTTP Cookie Manager then check:
header
parameter
ids that change between 2 recordings
just go to thread group and ptut infinite to 1
I have a jmeter test plan which has run 40000 threads and ramp up time is 600 seconds.
I am running it with command line.
./jmeter -n -t ../../HttpTestPlan.jmx
It runs fine on windows 64 bit machine. It able to execute all 40000 threads without any problem.
But when I run the same test plan in ec2 (with root privilege) it can execute only 31208 threads and then it will stop the execution.
What should I do to make sure it runs all the threads on linux ec2 box?
Thanks
2018-09-05 08:04:58,148 INFO o.a.j.u.JMeterUtils: Setting Locale to en_EN
2018-09-05 08:04:58,164 INFO o.a.j.JMeter: Loading user properties from: user.properties
2018-09-05 08:04:58,165 INFO o.a.j.JMeter: Loading system properties from: system.properties
2018-09-05 08:04:58,170 INFO o.a.j.JMeter: Copyright (c) 1998-2018 The Apache Software Foundation
2018-09-05 08:04:58,170 INFO o.a.j.JMeter: Version 4.0 r1823414
2018-09-05 08:04:58,170 INFO o.a.j.JMeter: java.version=1.8.0_181
2018-09-05 08:04:58,170 INFO o.a.j.JMeter: java.vm.name=OpenJDK 64-Bit Server VM
2018-09-05 08:04:58,170 INFO o.a.j.JMeter: os.name=Linux
2018-09-05 08:04:58,170 INFO o.a.j.JMeter: os.arch=amd64
2018-09-05 08:04:58,170 INFO o.a.j.JMeter: os.version=3.10.0-862.3.3.el7.x86_64
2018-09-05 08:04:58,171 INFO o.a.j.JMeter: file.encoding=UTF-8
2018-09-05 08:04:58,171 INFO o.a.j.JMeter: Max memory =1073741824
2018-09-05 08:04:58,171 INFO o.a.j.JMeter: Available Processors =2
2018-09-05 08:04:58,175 INFO o.a.j.JMeter: Default Locale=English (EN)
2018-09-05 08:04:58,175 INFO o.a.j.JMeter: JMeter Locale=English (EN)
2018-09-05 08:04:58,175 INFO o.a.j.JMeter: JMeterHome=/home/pardema/apache-jmeter-4.0
2018-09-05 08:04:58,175 INFO o.a.j.JMeter: user.dir =/home/pardema/apache-jmeter-4.0/bin
2018-09-05 08:04:58,176 INFO o.a.j.JMeter: PWD =/home/pardema/apache-jmeter-4.0/bin
2018-09-05 08:04:58,180 INFO o.a.j.JMeter: IP: xxxxxxxxxx Name: xxxxxxxxxxx: xxxxxxxxxxxxxx
2018-09-05 08:04:58,183 INFO o.a.j.s.FileServer: Default base='/home/pardema/apache-jmeter-4.0/bin'
2018-09-05 08:04:58,189 INFO o.a.j.s.FileServer: Set new base='/home/pardema/apache-jmeter-4.0/bin/../..'
2018-09-05 08:04:58,336 INFO o.a.j.s.SaveService: Testplan (JMX) version: 2.2. Testlog (JTL) version: 2.2
2018-09-05 08:04:58,355 INFO o.a.j.s.SaveService: Using SaveService properties file encoding UTF-8
2018-09-05 08:04:58,360 INFO o.a.j.s.SaveService: Using SaveService properties version 4.0
2018-09-05 08:04:58,366 INFO o.a.j.s.SaveService: Loading file: ../../HttpTestPlan.jmx
2018-09-05 08:04:58,409 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/html is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2018-09-05 08:04:58,409 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for application/xhtml+xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2018-09-05 08:04:58,409 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for application/xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2018-09-05 08:04:58,409 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/xml is org.apache.jmeter.protocol.http.parser.LagartoBasedHtmlParser
2018-09-05 08:04:58,410 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/vnd.wap.wml is org.apache.jmeter.protocol.http.parser.RegexpHTMLParser
2018-09-05 08:04:58,410 INFO o.a.j.p.h.s.HTTPSamplerBase: Parser for text/css is org.apache.jmeter.protocol.http.parser.CssParser
2018-09-05 08:04:58,433 INFO o.a.j.JMeter: Creating summariser
2018-09-05 08:04:58,440 INFO o.a.j.e.StandardJMeterEngine: Running the test!
2018-09-05 08:04:58,441 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2018-09-05 08:04:58,441 INFO o.a.j.s.SampleEvent: List of sample_variables: []
2018-09-05 08:04:58,445 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must contain the string: '.functions.'
2018-09-05 08:04:58,445 INFO o.a.j.e.u.CompoundVariable: Note: Function class names must not contain the string: '.gui.'
2018-09-05 08:04:58,851 INFO o.a.j.JMeter: Running test (1536149098851)
2018-09-05 08:04:58,890 INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
2018-09-05 08:04:58,891 INFO o.a.j.e.StandardJMeterEngine: Starting 50000 threads for group Thread Group.
2018-09-05 08:04:58,891 INFO o.a.j.e.StandardJMeterEngine: Thread will continue on error
2018-09-05 08:04:58,891 INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=50000 ramp-up=600 perThread=12.0 delayedStart=false
2018-09-05 08:04:58,900 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
2018-09-05 08:04:58,913 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-2
2018-09-05 08:04:58,919 INFO o.a.j.p.h.s.HTTPHCAbstractImpl: Local host = 10-118-9-93.ebiz.verizon.com
2018-09-05 08:04:58,925 INFO o.a.j.p.h.s.HTTPHC4Impl: HTTP request retry count = 0
2018-09-05 08:04:58,932 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-3
2018-09-05 08:04:58,933 INFO o.a.j.s.SampleResult: Note: Sample TimeStamps are START times
2018-09-05 08:04:58,933 INFO o.a.j.s.SampleResult: sampleresult.default.encoding is set to ISO-8859-1
2018-09-05 08:04:58,933 INFO o.a.j.s.SampleResult: sampleresult.useNanoTime=true
2018-09-05 08:04:58,933 INFO o.a.j.s.SampleResult: sampleresult.nanoThreadSleep=5000
2018-09-05 08:04:58,946 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-4
2018-09-05 08:04:58,950 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-5
2018-09-05 08:04:58,962 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-6
2018-09-05 08:04:58,975 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-7
2018-09-05 08:04:59,001 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-9
2018-09-05 08:04:59,006 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-8
2018-09-05 08:04:59,026 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-10
2018-09-05 08:04:59,026 INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-11
You might need to amend /proc/sys/kernel/threads-max setting
Also check limits.conf as you may need to increase the maximum number of open handles
Be aware that 40k threads is quite big amount for a single JMeter engine so you might need to consider Distributed Testing , ensure that the machine(s) have enough headroom to operate in terms of CPU, RAM, network, disk IO, etc. as if JMeter will not be able to send requests fast enough you will get lower throughput even if your application will not be overloaded and stick to JMeter Best Practices.
Most probably you had a hs_err_pid.log file generated due to crash of your JVM.
Search for such file for root cause of JVM crash.
Among hypothesis:
Linux memory, process, file descriptor limits
Not enough memory on your system
Note that 40k threads requires a powerful machine and most probably more than one to overcome:
- network limits of your card
- CPU
- Other resources required
Your machine (2 CPUs , 1Gb RAM) is very very short for that.
I am trying to load test my tcp server which is created using spring integration using JMeter. I am able to establish the connection with the server using TcpSampler in JMeter, but the server is unable to receive the text sent.
Below are my logs
INFO o.a.j.e.StandardJMeterEngine: Running the test!
INFO o.a.j.s.SampleEvent: List of sample_variables: []
INFO o.a.j.g.u.JMeterMenuBar: setRunning(true, *local*)
INFO o.a.j.e.StandardJMeterEngine: Starting ThreadGroup: 1 : Thread Group
INFO o.a.j.e.StandardJMeterEngine: Starting 1 threads for group Thread Group.
INFO o.a.j.e.StandardJMeterEngine: Test will stop abruptly on error
INFO o.a.j.t.ThreadGroup: Starting thread group... number=1 threads=1 ramp-up=1 perThread=1000.0 delayedStart=false
INFO o.a.j.t.ThreadGroup: Started thread group number 1
INFO o.a.j.e.StandardJMeterEngine: All thread groups have been started
INFO o.a.j.t.JMeterThread: Thread started: Thread Group 1-1
INFO o.a.j.p.t.s.TCPClientImpl: Using platform default charset:UTF-8
TcpServer accepts ByteArrayCrLfSerializer
In Jmeter, what should be EOL byte value?
Add a JSR223 Pre-Processor under your sampler with following code:
vars.put("LF",URLDecoder.decode("%0A", "ASCII"));
vars.put("CR",URLDecoder.decode("%0D", "ASCII"));
Then append to your TCP message:
${CR}${LF}