forked from jjeffery/stomp
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
heartbeat not response #66
Comments
Try setting |
I've encoutered that as well, i believe that there is an issue in the If the server receives a message, the |
anthonyraymond
added a commit
to anthonyraymond/stomp
that referenced
this issue
Jan 9, 2021
Whenever the reading loop was reading data it had the side effect of reseting the *writeTimeout* timer used to send heart beat to the client (this was due to variable scope). If the timer was rested too much in a row the heart beat will not occurred and it will end up in the client disconnecting. Fix go-stomp#66
worg
added a commit
that referenced
this issue
Jan 13, 2021
Fix heart beat problem in server/client/conn.go closes #66
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ActiveMQ: 5.15.9
Client:v2.0.3
ConnectOptions:
if no data is been sent for a while,
readTimeoutChannel
inprocessLoop
is triggerred.The text was updated successfully, but these errors were encountered: