Websockets aborting

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Websockets aborting

Centinaro, Gabriele
Hi,

I need to test the fact that my websockets stay open and then my server automatically gracefully closes them if no activity for 10 minutes.
I created a script that opens the WS and then a counter that waits for 10 minutes before checking if the WS is closed.

The issue I have is that the WS is aborted apparently by JMeter before the 10 minutes (usually after about 3-4 minutes).

Does anyone have experienced this and found a solution?

Thanks

Gabriele
Reply | Threaded
Open this post in threaded view
|

Re: Websockets aborting

glinius@live.com
Make sure to provide *Read Timeout* to be at least 600000 milliseconds (10
minutes)

It can be done in the Open Connection Sampler (from  JMeter WebSocket
Samplers by Peter Doornbosch
<https://github.com/ptrd/jmeter-websocket-samplers>  )

<http://www.jmeter-archive.org/file/t340375/foo.png>

If you will still be experiencing problems - consider  increasing JMeter
logging verbosity
<https://www.blazemeter.com/blog/how-to-configure-jmeter-logging/>   for the
WebSocket components by adding the next line to /log4j2.xml/ file (lives in
"bin" folder of your JMeter installation)


> <Logger name="eu.luminis" level="debug" />





--
Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [EXTERNAL] Re: Websockets aborting

Centinaro, Gabriele
Thanks for the reply,

Unfortunately none of the 2 changes did help.
I am still not able to keep my WS open. They get aborted after 3-4 minutes of inactivity.

Gabriele

-----Original Message-----
From: [hidden email] <[hidden email]>
Sent: Monday, March 2, 2020 7:59 AM
To: [hidden email]
Subject: [EXTERNAL] Re: Websockets aborting

Make sure to provide *Read Timeout* to be at least 600000 milliseconds (10
minutes)

It can be done in the Open Connection Sampler (from  JMeter WebSocket Samplers by Peter Doornbosch <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ptrd_jmeter-2Dwebsocket-2Dsamplers&d=DwICAg&c=h-HJQ5E3_Jo9moAvrfQA-w&r=al56mFAmGHTrmRMfinr9RLH64eocDNGIEreGS1nG9pU&m=YhqsNrW3lEBzsJEd15YGbjNhs4B-gd2qsVM-vNZuwiU&s=bKwqWqeWW8Rm3FqMORVOFf7tM3bDKcxbwH8XgaGiV1c&e= >  )

<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.jmeter-2Darchive.org_file_t340375_foo.png&d=DwICAg&c=h-HJQ5E3_Jo9moAvrfQA-w&r=al56mFAmGHTrmRMfinr9RLH64eocDNGIEreGS1nG9pU&m=YhqsNrW3lEBzsJEd15YGbjNhs4B-gd2qsVM-vNZuwiU&s=hro60dIxDbL0YClXJKPfrMTjcHQIkQGRqtHhBbQJsOg&e= >

If you will still be experiencing problems - consider  increasing JMeter logging verbosity
<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.blazemeter.com_blog_how-2Dto-2Dconfigure-2Djmeter-2Dlogging_&d=DwICAg&c=h-HJQ5E3_Jo9moAvrfQA-w&r=al56mFAmGHTrmRMfinr9RLH64eocDNGIEreGS1nG9pU&m=YhqsNrW3lEBzsJEd15YGbjNhs4B-gd2qsVM-vNZuwiU&s=b9v3Ttg65nW9J2zbs7YNhK15vQn7H7Dc_KTpXHWd8YU&e= >   for the
WebSocket components by adding the next line to /log4j2.xml/ file (lives in "bin" folder of your JMeter installation)


> <Logger name="eu.luminis" level="debug" />





--
Sent from: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.jmeter-2Darchive.org_JMeter-2DUser-2Df512775.html&d=DwICAg&c=h-HJQ5E3_Jo9moAvrfQA-w&r=al56mFAmGHTrmRMfinr9RLH64eocDNGIEreGS1nG9pU&m=YhqsNrW3lEBzsJEd15YGbjNhs4B-gd2qsVM-vNZuwiU&s=FVXccPPslwlr88k3zprm8SyiNr2kHSOxmFT0O3Ag5FI&e= 

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]