Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0BB2B200CAF for ; Thu, 22 Jun 2017 17:11:29 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0A6E8160BE7; Thu, 22 Jun 2017 15:11:29 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4C0EA160BE5 for ; Thu, 22 Jun 2017 17:11:28 +0200 (CEST) Received: (qmail 93949 invoked by uid 500); 22 Jun 2017 15:11:27 -0000 Mailing-List: contact issues-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@jmeter.apache.org Delivered-To: mailing list issues@jmeter.apache.org Received: (qmail 93937 invoked by uid 99); 22 Jun 2017 15:11:25 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2017 15:11:25 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 3CE9B1857B1 for ; Thu, 22 Jun 2017 15:11:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.499 X-Spam-Level: X-Spam-Status: No, score=0.499 tagged_above=-999 required=6.31 tests=[KAM_NUMSUBJECT=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id qvOn8QmXHVGE for ; Thu, 22 Jun 2017 15:11:23 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id E5A5B5F5CC for ; Thu, 22 Jun 2017 15:11:21 +0000 (UTC) Received: from asf-bz1-us-mid.priv.apache.org (nat1-us-mid.apache.org [23.253.172.122]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTPS id 2FCD0E00A3 for ; Thu, 22 Jun 2017 15:11:21 +0000 (UTC) Received: by asf-bz1-us-mid.priv.apache.org (ASF Mail Server at asf-bz1-us-mid.priv.apache.org, from userid 33) id 6E8B360DFB; Thu, 22 Jun 2017 15:11:18 +0000 (UTC) From: bugzilla@apache.org To: issues@jmeter.apache.org Subject: [Bug 61209] New: Save Responses to a File does not seem to be thread safe in Jmeter 3.2 Date: Thu, 22 Jun 2017 15:11:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: JMeter X-Bugzilla-Component: Main X-Bugzilla-Version: 3.2 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: edcrane@itzed-solutions.co.uk X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: issues@jmeter.apache.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bz.apache.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 archived-at: Thu, 22 Jun 2017 15:11:29 -0000 https://bz.apache.org/bugzilla/show_bug.cgi?id=3D61209 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: issues@jmeter.apache.org Reporter: edcrane@itzed-solutions.co.uk 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 (C= SV 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 file= name 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 t= hat not all of the 200 files were created, some were at random skipped. I did s= ome 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 sa= ved I get filename_10_1,filename_10_2,filename_10_2,filename_10_2 .... etc sav= ed. 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 uniq= ue 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 --=20 You are receiving this mail because: You are the assignee for the bug.=