https://bz.apache.org/bugzilla/show_bug.cgi?id=61209
Bug ID: 61209
Summary: Save Responses to a File does not seem to be thread
safe in Jmeter 3.2
Product: JMeter
Version: 3.2
Hardware: Other
OS: Linux
Status: NEW
Severity: major
Priority: P2
Component: Main
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
I am using Jmeter 3.2 via the jmeter-maven-plugin (2.2.0) via jenkins
I'm not sure whether this would be an issue with JMeter or the plugin. But I
have to raise an issue on one first and I chose Jmeter.
I have a simple jmx file which reads a single line or data from CSV file (CSV
Data Set Config), uses the CSV data to build a SQL query to a DB via JDBC
Request and then uses Save Responses to a File to save the data into a filename
which is created using the CSV data (identical to the CSV Data used in the SQL
query).
The thread group in the JMX runs 200 threads with a rampup of 1s
I was previously using Jmeter 2.13 via the jmeter-maven-plugin (1.10.1) via
jenkins. With this version all of the 200 unique files are always generated.
When I switched to Jmeter 3.2 via the jmeter-maven-plugin (2.2.0) I found that
not all of the 200 files were created, some were at random skipped. I did some
digging in the *.log and found;
CSV Data Set Config opens the config files (based on threadnum) 1-200 as
expected
JDBC Request sends 200 unique queries based on the CSV data as expected
Save Responses to a File writes 200 files, but some filenames are saved more
than once. i.e. instead of
filename_10_1,filename_10_2,filename_10_10,filename_10_19 .....etc being saved
I get filename_10_1,filename_10_2,filename_10_2,filename_10_2 .... etc saved.
Resulting in a variable number of filenames being created. But less than the
200 expected
So to debug further I set the rampup to 200 ... so that none of the threads
would overlap (DB response is 5-30ms). When slowed down all of the 200 unique
filenames are saved.
This indicates to me that something within the Save Responses to a File is not
Thread Safe ... as when the threads run concurrently there are issues .
I am running on Ubuntu 16.04
I couldn't find any issues already covering this fault. If you need further
information please let me know
--
You are receiving this mail because:
You are the assignee for the bug.
