You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears based on logging server status the websocket issues a reconnect attempt once and then hangs where as the node transport with the same configuration is retrying
It's worth noting I did observe the websocket connection reconnect once if I killed and restarted my server very quickly.
Expected behavior
As both transports accept the same argument set ConnectionOptions from nats-core I would expect their behaviors to be identical.
Server and client version
Server version: 2.10.21
NATS core version: 3.0.0-51
Host environment
No response
Steps to reproduce
Using node 22, connect using the two examples provided in Observed Behavior. Run the following code with your connection, killing your server and restarting after a few seconds, the websocket connection will not be restored while the node transport connection will be.
Observed behavior
When using the following websocket connection config, if the server is killed and then restarted the connection is not restored.
While the same configuration using the node transport does reconnect.
It appears based on logging server status the websocket issues a reconnect attempt once and then hangs where as the node transport with the same configuration is retrying
It's worth noting I did observe the websocket connection reconnect once if I killed and restarted my server very quickly.
Expected behavior
As both transports accept the same argument set
ConnectionOptions
from nats-core I would expect their behaviors to be identical.Server and client version
Server version:
2.10.21
NATS core version:
3.0.0-51
Host environment
No response
Steps to reproduce
Using node 22, connect using the two examples provided in Observed Behavior. Run the following code with your connection, killing your server and restarting after a few seconds, the websocket connection will not be restored while the node transport connection will be.
The text was updated successfully, but these errors were encountered: