The end time for my BlazeMeter test is longer than configured.

book

Article ID: 220626

calendar_today

Updated On:

Products

BlazeMeter

Issue/Introduction

 

Hello,

I had a test scheduled to run for 2:20 minutes.
The start time and end time are longer than the 2:20 minutes but the test duration says it was 2:20 minutes.

Why is this happening?

 

Cause

 

Jmeter hung threads will time out after 30 minutes.

Environment

 

BLAZEMETER PERFORMANCE TESTING
SAAS

Resolution

 

The reason the time extended past the original configured 2:20 minutes usually is caused by a hung thread
in which case Blazemeter will wait for a default of 30 minutes for the threads to try and exist gracefully and then kill them.

we can see this from the Jmeter logs.
r-v4-6100282fb9458795384542
 Line 1230: 2021-07-27 18:45:29,304 WARN o.a.j.t.JMeterThread: Interrupting: 360_HCA_OP_StartCod_v21.7-ThreadStarter 1-29 sampler: /Data360/api/genericdata/op/initialload-236
 Line 1231: 2021-07-27 18:45:29,308 WARN o.a.j.t.JMeterThread: Interrupting: 360_HCA_OP_StartCod_v21.7-ThreadStarter 1-77 sampler: /Data360/api/genericdata/op/initialload-385
 Line 1239: 2021-07-27 18:45:29,311 WARN o.a.j.t.JMeterThread: Interrupting: 360_HCA_OP_StartCod_v21.7-ThreadStarter 1-56 sampler: /3M_360App/package/name-SystemAbout/-245

r-v4-61002830bc4e0152198589
 Line 295: 2021-07-27 18:46:25,060 WARN o.a.j.t.JMeterThread: Interrupting: 360_HCA_CDI_v21.7_B522-ThreadStarter 1-38 sampler: /3M_360App/Content/ng/FindingsDialog-177
 Line 297: 2021-07-27 18:46:25,061 WARN o.a.j.t.JMeterThread: Interrupting: 360_HCA_CDI_v21.7_B522-ThreadStarter 1-1 sampler: /webcv-98
 Line 300: 2021-07-27 18:46:25,063 WARN o.a.j.t.JMeterThread: Interrupting: 360_HCA_CDI_v21.7_B522-ThreadStarter 1-27 sampler: /3M_360App/Content/ng/reviewersummary-64
 Line 302: 2021-07-27 18:46:25,063 WARN o.a.j.t.JMeterThread: Interrupting: 360_HCA_CDI_v21.7_B522-ThreadStarter 1-11 sampler: /3M_360App/dashboard-23
 Line 303: 2021-07-27 18:46:25,064 WARN o.a.j.t.JMeterThread: Interrupting: 360_HCA_CDI_v21.7_B522-ThreadStarter 1-14 sampler: /3M_360App/-22

r-v4-610028308ab95950214079
 Line 75: 2021-07-27 17:45:44,925 WARN o.a.j.t.JMeterThread: Interrupting: HCA_Reports_HIM Coding Report_CVS-ThreadStarter 1-1 sampler: Flow Control Action

Additional Information

The application log of the application being tested can be consulted to find out why threads hang.

Attachments