This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 32
Multiple connection #218
Comments
The v8 has some additional logic, which may cause this behavior. Please share your configuration and debug output. |
Config
Init
App module
|
Thanks for the detailed diagnostic report. One new feature was intorduced in v8 of this library - https://stomp-js.github.io/guide/stompjs/rx-stomp/upgrading-to-stompjs-6-rx-stomp-1.html#connectiontimeout (https://stomp-js.github.io/api-docs/latest/classes/Client.html#connectionTimeout). It seems it does not work as intended in every case. Set it to |
It worked. Thank's |
Released @stomp/[email protected] and @stomp/[email protected]. It sets https://stomp-js.github.io/api-docs/latest/classes/Client.html#connectionTimeout to 0 to de-activate this feature. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using the follow configuration manual: #121 (comment)
Angular: 9.0.7
@stomp/ng2-stompjs: 8.0.0
I am simulating loss of connection with the server. When the library tries to reconnect, some requests / sessions are made successfully. Instead of just one. Check images below
All status 101 is successful
First connection successful
Second connection successful
The text was updated successfully, but these errors were encountered: