You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jmeter.apache.org by Philippe Mouawad <p....@ubik-ingenierie.com> on 2017/08/17 14:23:25 UTC
Bug 61395
Hello,
Anybody has an idea regarding:
*Bug 61395* <https://bz.apache.org/bugzilla/show_bug.cgi?id=61395> - Large
server response got blocked during recording
Thanks
--
Cordialement.
Philippe Mouawad.
Ubik-Ingénierie
UBIK LOAD PACK Web Site <http://www.ubikloadpack.com/>
UBIK LOAD PACK on TWITTER <https://twitter.com/ubikloadpack>
Re: Bug 61395
Posted by Alexander Podelko <ap...@yahoo.com.INVALID>.
Yes, correct. Exactly the same request with less data (just smaller in size) get recorded without any issue.
On Thursday, August 17, 2017, 11:34:00 AM EDT, Philippe Mouawad <ph...@gmail.com> wrote:
Hi Felix,I don't think so, I think this failure is for another URL.Alexander could confirm that the succeeding url has same scheme ?
Regards
On Thursday, August 17, 2017, Felix Schumacher <fe...@internetallee.de> wrote:
Am 17.08.2017 um 16:23 schrieb Philippe Mouawad:
Hello,
Anybody has an idea regarding:
*Bug 61395* <https://bz.apache.org/bugzill a/show_bug.cgi?id=61395> - Large
server response got blocked during recording
Could it be cert related?
2017-07-31 13:56:33,502 WARN o.a.j.p.h.p.Proxy: [34609] Problem with SSL certificate for 'incoming.telemetry.mozilla.or g'? Ensure browser is set to accept the JMeter proxy cert: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Software caused connection abort: recv failed
Felix
Thanks
--
Cordialement.
Philippe Mouawad.
Re: Bug 61395
Posted by Philippe Mouawad <ph...@gmail.com>.
For information, changing this setting did the trick.
Although I understand that as it trimmed the response it didn't render
correctly in the browser, It is not clear why it didn't create the sample
so there is clearly a bug here.
And besides, during recording the trimming should be avoided.
Regards
On Thursday, August 17, 2017, Philippe Mouawad <ph...@gmail.com>
wrote:
> FI
>
> ---------- Forwarded message ----------
> From: *Alexander Podelko* <apodelko@yahoo.com
> <javascript:_e(%7B%7D,'cvml','apodelko@yahoo.com');>>
> Date: Thursday, August 17, 2017
> Subject: Bug 61395
> To: Philippe Mouawad <philippe.mouawad@gmail.com
> <javascript:_e(%7B%7D,'cvml','philippe.mouawad@gmail.com');>>
>
>
> Hi Philippe,
>
>
> Partial success. The response now got back - so I see the response in
> browser, app is working.
>
> However I don't see the request itself
>
> [17/Aug/2017:14:05:20 -0700] "GET /dmcs/rest/v1/requests/7dd143f
> c-4e28-49e9-ab0b-7dcb77f2eb4a/items?expand=item.validations&_=1503003807493
> HTTP/1.1" 200 11771576
>
> to be recorded by JMeter.
>
> Attaching the script, log, and recording.
>
> Thanks,
> Alex
>
>
>
> On Thursday, August 17, 2017, 11:40:25 AM EDT, Philippe Mouawad <
> philippe.mouawad@gmail.com> wrote:
>
>
> Hi Alexander,
> Could you try setting in user.properties
>
> httpsampler.max_bytes_to_store_per_request=20000000
>
> And see if it works ?
>
> Thanks
>
>
>
> On Thursday, August 17, 2017, Philippe Mouawad <ph...@gmail.com>
> wrote:
>
> Hi Felix,
> I don't think so, I think this failure is for another URL.
> Alexander could confirm that the succeeding url has same scheme ?
>
>
> Regards
>
> On Thursday, August 17, 2017, Felix Schumacher <felix.schumacher@
> internetallee.de> wrote:
>
> Am 17.08.2017 um 16:23 schrieb Philippe Mouawad:
>
> Hello,
> Anybody has an idea regarding:
>
> *Bug 61395* <https://bz.apache.org/bugzill a/show_bug.cgi?id=61395
> <https://bz.apache.org/bugzilla/show_bug.cgi?id=61395>> - Large
> server response got blocked during recording
>
> Could it be cert related?
>
> 2017-07-31 13:56:33,502 WARN o.a.j.p.h.p.Proxy: [34609] Problem with SSL
> certificate for 'incoming.telemetry.mozilla.or g
> <http://incoming.telemetry.mozilla.org>'? Ensure browser is set to accept
> the JMeter proxy cert: Connection has been shutdown:
> javax.net.ssl.SSLException: java.net.SocketException: Software caused
> connection abort: recv failed
>
> Felix
>
>
> Thanks
>
>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
--
Cordialement.
Philippe Mouawad.
Fwd: Bug 61395
Posted by Philippe Mouawad <ph...@gmail.com>.
FI
---------- Forwarded message ----------
From: *Alexander Podelko* <ap...@yahoo.com>
Date: Thursday, August 17, 2017
Subject: Bug 61395
To: Philippe Mouawad <ph...@gmail.com>
Hi Philippe,
Partial success. The response now got back - so I see the response in
browser, app is working.
However I don't see the request itself
[17/Aug/2017:14:05:20 -0700] "GET /dmcs/rest/v1/requests/
7dd143fc-4e28-49e9-ab0b-7dcb77f2eb4a/items?expand=item.validations&_=1503003807493
HTTP/1.1" 200 11771576
to be recorded by JMeter.
Attaching the script, log, and recording.
Thanks,
Alex
On Thursday, August 17, 2017, 11:40:25 AM EDT, Philippe Mouawad <
philippe.mouawad@gmail.com
<javascript:_e(%7B%7D,'cvml','philippe.mouawad@gmail.com');>> wrote:
Hi Alexander,
Could you try setting in user.properties
httpsampler.max_bytes_to_store_per_request=20000000
And see if it works ?
Thanks
On Thursday, August 17, 2017, Philippe Mouawad <philippe.mouawad@gmail.com
<javascript:_e(%7B%7D,'cvml','philippe.mouawad@gmail.com');>> wrote:
Hi Felix,
I don't think so, I think this failure is for another URL.
Alexander could confirm that the succeeding url has same scheme ?
Regards
On Thursday, August 17, 2017, Felix Schumacher <felix.schumacher@
internetallee.de> wrote:
Am 17.08.2017 um 16:23 schrieb Philippe Mouawad:
Hello,
Anybody has an idea regarding:
*Bug 61395* <https://bz.apache.org/bugzill a/show_bug.cgi?id=61395
<https://bz.apache.org/bugzilla/show_bug.cgi?id=61395>> - Large
server response got blocked during recording
Could it be cert related?
2017-07-31 13:56:33,502 WARN o.a.j.p.h.p.Proxy: [34609] Problem with SSL
certificate for 'incoming.telemetry.mozilla.or g
<http://incoming.telemetry.mozilla.org>'? Ensure browser is set to accept
the JMeter proxy cert: Connection has been shutdown:
javax.net.ssl.SSLException: java.net.SocketException: Software caused
connection abort: recv failed
Felix
Thanks
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
--
Cordialement.
Philippe Mouawad.
Re: Bug 61395
Posted by Philippe Mouawad <ph...@gmail.com>.
Hi Alexander,
Could you try setting in user.properties
httpsampler.max_bytes_to_store_per_request=20000000
And see if it works ?
Thanks
On Thursday, August 17, 2017, Philippe Mouawad <ph...@gmail.com>
wrote:
> Hi Felix,
> I don't think so, I think this failure is for another URL.
> Alexander could confirm that the succeeding url has same scheme ?
>
>
> Regards
>
> On Thursday, August 17, 2017, Felix Schumacher <felix.schumacher@
> internetallee.de
> <javascript:_e(%7B%7D,'cvml','felix.schumacher@internetallee.de');>>
> wrote:
>
>> Am 17.08.2017 um 16:23 schrieb Philippe Mouawad:
>>
>>> Hello,
>>> Anybody has an idea regarding:
>>>
>>> *Bug 61395* <https://bz.apache.org/bugzilla/show_bug.cgi?id=61395> -
>>> Large
>>> server response got blocked during recording
>>>
>> Could it be cert related?
>>
>> 2017-07-31 13:56:33,502 WARN o.a.j.p.h.p.Proxy: [34609] Problem with SSL
>> certificate for 'incoming.telemetry.mozilla.org'? Ensure browser is set
>> to accept the JMeter proxy cert: Connection has been shutdown:
>> javax.net.ssl.SSLException: java.net.SocketException: Software caused
>> connection abort: recv failed
>>
>> Felix
>>
>>
>>> Thanks
>>>
>>>
>>>
>>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>
>
--
Cordialement.
Philippe Mouawad.
Re: Bug 61395
Posted by Philippe Mouawad <ph...@gmail.com>.
Hi Felix,
I don't think so, I think this failure is for another URL.
Alexander could confirm that the succeeding url has same scheme ?
Regards
On Thursday, August 17, 2017, Felix Schumacher <
felix.schumacher@internetallee.de> wrote:
> Am 17.08.2017 um 16:23 schrieb Philippe Mouawad:
>
>> Hello,
>> Anybody has an idea regarding:
>>
>> *Bug 61395* <https://bz.apache.org/bugzilla/show_bug.cgi?id=61395> -
>> Large
>> server response got blocked during recording
>>
> Could it be cert related?
>
> 2017-07-31 13:56:33,502 WARN o.a.j.p.h.p.Proxy: [34609] Problem with SSL
> certificate for 'incoming.telemetry.mozilla.org'? Ensure browser is set
> to accept the JMeter proxy cert: Connection has been shutdown:
> javax.net.ssl.SSLException: java.net.SocketException: Software caused
> connection abort: recv failed
>
> Felix
>
>
>> Thanks
>>
>>
>>
>
--
Cordialement.
Philippe Mouawad.
Re: Bug 61395
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 17.08.2017 um 16:23 schrieb Philippe Mouawad:
> Hello,
> Anybody has an idea regarding:
>
> *Bug 61395* <https://bz.apache.org/bugzilla/show_bug.cgi?id=61395> - Large
> server response got blocked during recording
Could it be cert related?
2017-07-31 13:56:33,502 WARN o.a.j.p.h.p.Proxy: [34609] Problem with SSL
certificate for 'incoming.telemetry.mozilla.org'? Ensure browser is set
to accept the JMeter proxy cert: Connection has been shutdown:
javax.net.ssl.SSLException: java.net.SocketException: Software caused
connection abort: recv failed
Felix
>
> Thanks
>
>