WebSocket connection limitation issue?

[GTakacs 0]

Hi All,

I have a QA which uses WebSocket to communicate with a device. Normaly everything is fine, BUT 
I wrote a loop what handle the connection lost and try to reconnect to the service. Works good, but nowadays I'v realized that this reconnect loop can't work for endless time and I think this is a bug.

After a lot of time to debug the issue I found that the problem is with the websocket client connection try count. After 240-245 try the whole QA running stopped. Not crashed, just absolutely doesn't do anything.

So this kind of operation you can't write a QA what can handle the websocket diconnection and reconnection event after a time. The time depends on the period which try to reconnect the client.

In the code you can see I use 30 secs to retry connecting. With this interval the QA can work for 2 hours. If I set this interval for 5 secs (this is the smallest value to let enpugh time to the websocket client to try to connect and timeout) this time reduced only to 20-21 minutes and the stops.

Have anybody issue with this before? The code (only the relevan parts) what I use:

 

Please login or register to see this code.

 

Edited May 8, 2024 by GTakacs