https://bz.apache.org/bugzilla/show_bug.cgi?id=65213
Bug ID: 65213
Summary: Endurance Testing using jmeter stopped abruptly in
distributed environment
Product: JMeter
Version: 5.2.1
Hardware: Other
OS: Linux
Status: NEW
Severity: critical
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: JMETER_5.5
I am using Azure Kubernetes Service(AKS) to deploy JMeter infrastructure. Using
JMeter - 5.2.1 version and Kubernetes version - 1.19.6.
I am running 24 hrs endurance test using JMeter with ThroughputShapingTimer. My
test stopped abruptly some time after 6 hrs and some time 8 hrs.
I checked jmeter-server.log file and getting warning - WARN
k.a.j.t.VariableThroughputTimer: No free threads left in worker pool.
No error observed in jmeter.log from jmeter slave.
I used 400 threads and then 800 threads and then tried 1100 threads still
getting - No free threads left in worker pool.
I increased jmeter slave and master memory from 2GB to 6GB and 4 cores of CPU
still issue persists.
I checked kubernetes PODS, they were not restarted so assuming there is Out of
Memory concern.
I ran with 2 slaves and 1 master also.
Please advise how to overcome this issue.
Following attachments are provided.
1. Test Plan
2. Jmeter-server.log file.
--
You are receiving this mail because:
You are the assignee for the bug.
