-
Notifications
You must be signed in to change notification settings - Fork 154
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Client doesn't reconnect with TLS #32
Comments
We didn't have a test for this. Baaaad developer (hint: me). Thanks for catching this! |
@mcqueary do you agree this is critical? I mean, the workaround is to not use TLS on NATS 👎 . |
I do indeed. Looking at code today. If you're on slack I'd like to chat On Friday, July 22, 2016, Paulo Pires notifications@github.com wrote:
Larry McQueary | Director, Messaging Technology |
hi @mcqueary any updates? Branch |
@mcqueary - Would you like another set of eyes on this? |
I'm willing to help as well. |
FYI, tried with Steps to reproduce:
|
My client code:
Now, the connection works and I have thousands of subscriptions and publishers working for days.
But at a certain moment in time, the client disconnects and never reconnects.
I'm sorry about the log format, but I'm using a Logstash-like encoder for further log processing. Also, order is from newest to oldest:
On the server side, again from newest to oldest:
I wonder why TLS handhake fails. It seems flushing is happening before TLS handshake is done.
The text was updated successfully, but these errors were encountered: