eSeGeCe
software
Good morning,
With Esegece v4.4.0 - 2020 May (and the previous release also) I'm experiencing the problem described in the subject.
In this zip file you will find:
With Esegece v4.4.0 - 2020 May (and the previous release also) I'm experiencing the problem described in the subject.
In this zip file you will find:
- Source code to recreate the problem.
- The compiled executable.
- A video showing the issue and how to reproduce it.
- Information about the testing environment.
Hi,
I've been analyzing the code and watchdog was working as designed, basically watchdog every time there is a disconnection, starts an internal timer and try to reconnect again. The problem here was that when client connects to Server, websocket connection was established successfully and after that, server checks username and closes the connection. So, for watchdog, connection was successful, so was trying to reconnect one time and another.
I've done some changes, so when mqtt protocol is enabled, instead of use WebSocket connection, use MQTT connection event, so will avoid this problem when using Attempts property. I've updated latest beta and will be available for next release.
Thanks for the feedback.
Kind Regards,
Sergio
I've been analyzing the code and watchdog was working as designed, basically watchdog every time there is a disconnection, starts an internal timer and try to reconnect again. The problem here was that when client connects to Server, websocket connection was established successfully and after that, server checks username and closes the connection. So, for watchdog, connection was successful, so was trying to reconnect one time and another.
I've done some changes, so when mqtt protocol is enabled, instead of use WebSocket connection, use MQTT connection event, so will avoid this problem when using Attempts property. I've updated latest beta and will be available for next release.
Thanks for the feedback.
Kind Regards,
Sergio
- Page :
- 1
There are no replies made for this post yet.