Bug 57013 - use multiple bytes to define the termination of response in TCP Sampler
Summary: use multiple bytes to define the termination of response in TCP Sampler
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.11
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-24 08:57 UTC by harry_no_spot
Modified: 2014-10-21 02:09 UTC (History)
1 user (show)


Attachments
tcp sampler response (46.24 KB, image/png)
2014-10-21 02:09 UTC, harry_no_spot 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description harry_no_spot 2014-09-24 08:57:30 UTC 
Test Plan - Thread Group - TCP Sampler - End of line(EOL) byte value:

for most cases, use multiple bytes to define the termination of response is better than single byte.
Comment 1 Philippe Mouawad 2014-10-19 12:25:54 UTC 
Hello,
Can you give some examples ?
And detail a bit more your request ?
Thanks
Comment 2 harry_no_spot 2014-10-21 02:08:28 UTC 
in my example, I set 'End of line(EOL) byte value' to 0.
the example works ok.
if the response is not sent back as a whole packet, i.e. for some reason, the packet is split to 2 parts, and the first part is just ended with 00, if the first part is readed by jmeter, then the second part will not be read. 
plz refer to the attachment picture.

btw, I think 'End of line(EOL) byte value' should be parsed as hexdecimal format.
Comment 3 harry_no_spot 2014-10-21 02:09:49 UTC 
Created attachment 32130 [details]
tcp sampler response