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
When there is a subject that is long enough, it will cause the connection to close. But the fatal problem is that it will not automatically reconnect and recover. Only when I restart the entire Go application service will it recover.
Expected behavior
It is hoped that even if an error occurs, it will not affect the closure of the connection; otherwise, it will be fatal to the service.
Of course, if it's because of a naming issue, I hope it can tell me the reason for the error instead of disconnecting the connection.
Server and client version
go: go1.21.6 darwin/arm64
nats.go: v1.33.1
nat-server: v2.10.11
Host environment
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered:
Observed behavior
This is an example of my stress test:
Result:
Question:
When there is a subject that is long enough, it will cause the connection to close. But the fatal problem is that it will not automatically reconnect and recover. Only when I restart the entire Go application service will it recover.
Expected behavior
Server and client version
go
:go1.21.6 darwin/arm64
nats.go
:v1.33.1
nat-server
:v2.10.11
Host environment
No response
Steps to reproduce
No response
The text was updated successfully, but these errors were encountered: