jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Mouawad <philippe.moua...@gmail.com>
Subject Re: simple writer question
Date Tue, 07 Mar 2017 20:04:03 GMT
Just for followup.
Bo answered in another thread:

The following resolved the problem:

Change the from what is given in the original e-mail to the following:

<url>true</url>
<threadCounts>false</threadCounts>

This now works as intended. I do not understand why "threadCounts" was not
coming up in the .jmx file



Regards

On Mon, Mar 6, 2017 at 10:10 PM, Bo Bodnar <bbodnar@us.ibm.com> wrote:

>
>
> I'm running a jmeter 2.13 script and have an interesting problem in a
> simple data writer that I can't resolve.  I'm hoping someone here has seen
> this before and figured out a solution.  The details:
>
> I've a simple data writer where I want the output to be just the URL call.
> Using the GUI, I uncheck everything except "Save URL".  Running jmeter from
> the GUI now works exactly as desired.  For example, I get something like in
> the log file:
>
> http://10.155.64.15/BO/d99c62e2-707c-4edc-99e2-43abca746d5a_81KB
>
> I now save the script, turn off the GUI, and run the .jmx script from the
> command line.  Instead of getting just the URL, I get thread information;
> e.g.:
>
> 1,1,http://10.155.64.15/BO/cbdce96a-119d-43e7-a6ff-4c1a22338a0f_14.1KB
>
> In other words, the "1,1," should not be present.  I then turn on the GUI,
> open the pertinent .jmx file, and see that "Save Active Thread Counts" is
> now checked (recall that it was unchecked).  When I look at the .jmx file,
> I see that thread information is unchecked (as intended).  The portion of
> the .jmx file that pertains to this simple writer is:
>
> <ResultCollector guiclass="SimpleDataWriter" testclass="ResultCollector"
> testname="Simple Data Writer - Success" enabled="true">
>           <boolProp name="ResultCollector.error_logging">false</boolProp>
>           <objProp>
>             <name>saveConfig</name>
>             <value class="SampleSaveConfiguration">
>               <time>false</time>
>               <latency>false</latency>
>               <timestamp>false</timestamp>
>               <success>false</success>
>               <label>false</label>
>               <code>false</code>
>               <message>false</message>
>               <threadName>false</threadName>
>               <dataType>false</dataType>
>               <encoding>false</encoding>
>               <assertions>false</assertions>
>               <subresults>false</subresults>
>               <responseData>false</responseData>
>               <samplerData>false</samplerData>
>               <xml>false</xml>
>               <fieldNames>false</fieldNames>
>               <responseHeaders>false</responseHeaders>
>               <requestHeaders>false</requestHeaders>
>               <responseDataOnError>false</responseDataOnError>
>
> <saveAssertionResultsFailureMessage>false</saveAssertionResultsFailureMes
> sage>
>               <assertionsResultsToSave>0</assertionsResultsToSave>
>               <url>true</url>
>             </value>
>           </objProp>
>           <stringProp name="filename">${WriteURLsToFolder}/$
> {OutputFilePrefix}_${__time(yyyy_MM_dd_HH_mm_ss)}.log</stringProp>
>
> It appears to me that the simple writer is broken for this scenario.  Is
> this some way of working around this?
>
> Thank you,
>
> Bo
>
>
>
>
>    Bohdan L. Bodnar
>    Lead Performance Engineer
>    1-312-871-5163
>
>
>
>
>    E-mail: bbodnar@us.ibm.com                               222 South
> Riverside Plaza
>
> Chicago, IL 60606
>
> United States
>
>


-- 
Cordialement.
Philippe Mouawad.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message