jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jonathan Radon <JRa...@routeone.com>
Subject RE: Simple Data Writer not closing file until end of test plan
Date Thu, 09 Jun 2016 20:31:23 GMT
That's it!  Changing the value of jmeter.save.saveservice.autoflush corrected the issue.  Thank
you.

-----Original Message-----
From: Deepak Shetty [mailto:shettyd@gmail.com]
Sent: Tuesday, June 07, 2016 8:02 PM
To: JMeter Users List
Subject: Re: Simple Data Writer not closing file until end of test plan

Hi
Can you try changing the value of jmeter.save.saveservice.autoflush in jmeter.properties (note
side effect of reduced performance) - This might be why the SimpleDataWriter is not writing
data to file and I believe this changed in jmeter 2.10 jmeter.save.saveservice.autoflush=true

On Tue, Jun 7, 2016 at 4:37 PM, Deepak Shetty <shettyd@gmail.com> wrote:

> I'd say try with Save Responses to a file (assuming all the data you
> want is available in a response) - else write your own code to write
> to a file instead of using one of the listeners.
> or you could try to copy the file that your listener is writing into a
> new file (as a separate step) and then configure your CSV for that copied file.
>
> On Tue, Jun 7, 2016 at 1:45 PM, Jonathan Radon <JRadon@routeone.com>
> wrote:
>
>> I'm using JMeter 2.13 and have two thread groups.  The first is a
>> setup thread group that creates data in an external system.  It uses
>> extractors to pull various identifiers out of the responses from the external system.
>> The script then uses a Simple Data Writer to output the extracted
>> variables to CSV.  The second test thread group uses the CSV created
>> by the Simple Data Writer to feed data to its threads.
>>
>> This used to work in an older version of JMeter, but appears broken
>> in 2.13.  Based on the logs, it looks like the file isn't closed
>> until the end of the test plan.  I even went as far as to introduce a
>> middle thread group with a wait in it and manually inspected the CSV.
>> The CSV created by the setup thread group exists at that point, but
>> it's inaccessible / unreadable.  Once the test plan finishes the file is created
as expected.
>>
>> Am I doing something wrong?  Is this fixed in another version?  Any
>> ideas for a workaround?
>>
>> Logs included below.
>>
>> 2016/06/07 16:42:12 INFO  - jmeter.engine.StandardJMeterEngine:
>> Running the test!
>> 2016/06/07 16:42:12 INFO  - jmeter.samplers.SampleEvent: List of
>> sample_variables: [conversationId, organization, fsOrganization,
>> transactionSid, contractDpSid]
>> 2016/06/07 16:42:12 INFO  - jmeter.reporters.ResultCollector: Folder
>> C:\Users\jradon\Code\routeone\webapps\ec\ec-vault-core\target\jmeter\
>> tmp\20160607-164212
>> was created
>> 2016/06/07 16:42:12 INFO  - jmeter.gui.util.JMeterMenuBar:
>> setRunning(true,*local*)
>> 2016/06/07 16:42:12 INFO  - jmeter.engine.StandardJMeterEngine:
>> Starting setUp thread groups
>> 2016/06/07 16:42:12 INFO  - jmeter.engine.StandardJMeterEngine:
>> Starting setUp ThreadGroup: 1 : User Thread Group
>> 2016/06/07 16:42:12 INFO  - jmeter.engine.StandardJMeterEngine:
>> Starting
>> 1 threads for group User Thread Group.
>> 2016/06/07 16:42:12 INFO  - jmeter.engine.StandardJMeterEngine: Test
>> will stop on error
>> 2016/06/07 16:42:12 INFO  - jmeter.threads.ThreadGroup: Starting
>> thread group number 1 threads 1 ramp-up 1 perThread 1000.0
>> delayedStart=false
>> 2016/06/07 16:42:12 INFO  - jmeter.threads.ThreadGroup: Started
>> thread group number 1
>> 2016/06/07 16:42:12 INFO  - jmeter.engine.StandardJMeterEngine:
>> Waiting for all setup thread groups to exit
>> 2016/06/07 16:42:12 INFO  - jmeter.threads.JMeterThread: Thread started:
>> User Thread Group 1-1
>> 2016/06/07 16:42:16 INFO  - jmeter.threads.JMeterThread: Thread is done:
>> User Thread Group 1-1
>> 2016/06/07 16:42:16 INFO  - jmeter.threads.JMeterThread: Thread finished:
>> User Thread Group 1-1
>> 2016/06/07 16:42:16 INFO  - jmeter.engine.StandardJMeterEngine: All
>> Setup Threads have ended
>> 2016/06/07 16:42:16 INFO  - jmeter.engine.StandardJMeterEngine:
>> Starting
>> ThreadGroup: 1 : Transfer Of Ownership Thread Group
>> 2016/06/07 16:42:16 INFO  - jmeter.engine.StandardJMeterEngine:
>> Starting
>> 1 threads for group Transfer Of Ownership Thread Group.
>> 2016/06/07 16:42:16 INFO  - jmeter.engine.StandardJMeterEngine: Test
>> will stop on error
>> 2016/06/07 16:42:16 INFO  - jmeter.threads.ThreadGroup: Starting
>> thread group number 1 threads 1 ramp-up 1 perThread 1000.0
>> delayedStart=false
>> 2016/06/07 16:42:16 INFO  - jmeter.threads.ThreadGroup: Started
>> thread group number 1
>> 2016/06/07 16:42:16 INFO  - jmeter.engine.StandardJMeterEngine: All
>> thread groups have been started
>> 2016/06/07 16:42:16 INFO  - jmeter.threads.JMeterThread: Thread started:
>> Transfer Of Ownership Thread Group 1-1
>> 2016/06/07 16:42:16 INFO  - jmeter.services.FileServer: Stored:
>> C:\Users\jradon\Code\routeone\webapps\ec\ec-vault-core\target/jmeter/
>> tmp/20160607-164212/transferData.csv
>> 2016/06/07 16:42:16 INFO  - jmeter.threads.JMeterThread: Stop Thread
>> seen: org.apache.jorphan.util.JMeterStopThreadException: End of file
>> detected
>> 2016/06/07 16:42:16 INFO  - jmeter.threads.JMeterThread: Thread finished:
>> Transfer Of Ownership Thread Group 1-1
>> 2016/06/07 16:42:16 INFO  - jmeter.engine.StandardJMeterEngine:
>> Notifying test listeners of end of test
>> 2016/06/07 16:42:16 INFO  - jmeter.services.FileServer: Close:
>> C:\Users\jradon\Code\routeone\webapps\ec\ec-vault-core\target/jmeter/
>> tmp/20160607-164212/transferData.csv
>> 2016/06/07 16:42:16 INFO  - jmeter.gui.util.JMeterMenuBar:
>> setRunning(false,*local*)
>>
>>
>>
>>
>> CONFIDENTIALITY NOTE: This message and any attachments are
>> confidential, may contain information that is privileged and is
>> intended only for the use of the addressee. If you are not the
>> intended recipient or an authorized representative of the intended
>> recipient, you are hereby notified that any dissemination of this
>> communication is strictly prohibited. If you have received this
>> communication in error, please notify us immediately by e-mail and
>> delete the message and any attachments from your system. This message
>> is not meant to constitute an electronic signature or evidence intent to contract
electronically.
>>
>
>




CONFIDENTIALITY NOTE: This message and any attachments are confidential, may contain information
that is privileged and is intended only for the use of the addressee. If you are not the intended
recipient or an authorized representative of the intended recipient, you are hereby notified
that any dissemination of this communication is strictly prohibited. If you have received
this communication in error, please notify us immediately by e-mail and delete the message
and any attachments from your system. This message is not meant to constitute an electronic
signature or evidence intent to contract electronically.
Mime
View raw message