Closed artado closed 10 months ago
I have to say - I have no idea how to even start debugging this. If you can provide step by step instructions how to set up an environment with QNX and Azul JVM (or at least one of them so we can check which one is causing the issue), I can look into it.
Closing as I do not have a way to reproduce. If there is any update, let me know.
Description When clients is re-connecting to my WebSocket server there will be delay of "connectionLostTimeout" until handshake will be responded to client. Please let me know if you have any suggestions.
To Reproduce Steps to reproduce the behavior:
Please note: when I change the WebSocketServer connectionLostTimeout parameter to something a lot smaller than default 60 seconds (e.g. 2 seconds) -- re-connection & handshake will happen within a timeframe of a new connectionLostTimeout (e.g. 2 seconds). However in this case I risk to break the connection by Server side.
You can see the same in Wireshark log:
Example application to reproduce the issue
Expected behavior Expected that it will reconnect immediately.
Environment: Please note that this is running on embedded hardware, I do not have the same problem running the code on Linux or Windows.