You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2013/03/29 10:43:58 UTC
[Bug 54766] New: Response data is not saved to jtl in client's
machine , for the results captured from server engine
https://issues.apache.org/bugzilla/show_bug.cgi?id=54766
Bug ID: 54766
Summary: Response data is not saved to jtl in client's machine
, for the results captured from server engine
Product: JMeter
Version: 2.9
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: dimani2004@yahoo.co.uk
Classification: Unclassified
On both Client and Server Jmeter version : 2.9 r1437961
Both Client and Server : Windows
Client Jmeter properties:
jmeter.save.saveservice.response_data=true
while the following is being kept commented,
#jmeter.save.saveservice.response_data.on_error=false , which is false by
default.
When the test is remotely triggered by the Client, results are recorded to jtl,
listeners (summary, tree view, table).
But response data is not captured either to jtl. or to tree view -> response
data tab, unless there is an assertion failure.(but I have kept this
jmeter.save.saveservice.response_data.on_error to false).
What I wanted to see response data for successful runs and for failures as
well.
I have been trying my best to configure to get this thing worked. There is
nothing discussed about this topic in blogs too. Guessed this is some kind of
error.
More details:
Thread Name: Thread Group 1-1
Sample Start: 2013-03-29 14:54:34 IST
Load time: 8
Latency: 8
Size in bytes: 640
Headers size in bytes: 197
Body size in bytes: 443
Sample Count: 1
Error Count: 0
Response code: 200
Response message: OK
Response headers:
HTTP/1.1 200 OK
Date: Fri, 29 Mar 2013 09:24:28 GMT
Server: Apache
Content-Length: 443
Keep-Alive: timeout=15, max=90
Connection: Keep-Alive
Content-Type: application/x-json;charset=UTF-8
HTTPSampleResult fields:
ContentType: application/x-json;charset=UTF-8
DataEncoding: UTF-8
-------------------------
Thread Name: Thread Group 1-1
Sample Start: 2013-03-29 14:54:34 IST
Load time: 78
Latency: 48
Size in bytes: 509673
Headers size in bytes: 220
Body size in bytes: 509453
Sample Count: 1
Error Count: 0
Response code: 200
Response message: OK
Response headers:
HTTP/1.1 200 OK
Date: Fri, 29 Mar 2013 09:24:28 GMT
Server: Apache
Cache-Control: no-cache
Keep-Alive: timeout=15, max=93
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html;charset=UTF-8
HTTPSampleResult fields:
ContentType: text/html;charset=UTF-8
DataEncoding: UTF-8
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 54766] Response data is not saved to jtl in client's machine ,
for the results captured from server engine
Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=54766
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |p.mouawad@ubik-ingenierie.c
| |om
Resolution|--- |WORKSFORME
OS| |All
--- Comment #1 from Philippe Mouawad <p....@ubik-ingenierie.com> ---
This is not a bug.
Read this:
http://jmeter.apache.org/changes.html
Extract:
Some configuration defaults have changed to improve performances by
default(see Bug 54412 ), see description in New and Noteworthy section.
Distributed testing now uses MODE_STRIPPED_BATCH, which returns samples in
batch mode (every 100 samples or every minute by default). Note also that
MODE_STRIPPED_BATCH strips response data from SampleResult, so if you need it
change to another mode (mode property in jmeter.properties)
Result data are now saved to CSV by default
(jmeter.save.saveservice.output_format in jmeter.properties)
So you need to switch to another mode than stripped if you need response.
--
You are receiving this mail because:
You are the assignee for the bug.