Closed webonix closed 3 months ago
if the session timeouts, there is nothing the server thread can do to reconnect, because the connection get initialized by the client. only solution to this is see, is the possibility to set a custom idle or live timeout.
I resolved be having the client sending a heartbeat every 15 seconds
"problem" here is the idle timeout, i added support to set a custom idle timeout in 2 ways
commit: https://github.com/lucee/extension-websocket/commit/aa24b26fce7d3ed67f3564ce45d06b889be3d7ce
@michaeloffner nice :-)
what are all the option for the config file now?
{ "directory": "{lucee-config}/websockets/", "requestTimeout": 50, "idleTimeout": 300 }
directory = location of the components requestTimeout = timeout in seconds for a single request of a client idleTimeout = how long in seconds does a session idle before it get closed
BTW you can simply delete the json file and restart Lucee, then the extension will create the file new with al the option with the default values.
nice one, @michaeloffner Thank you
After connecting to Lucee WebSocket, then not doing anything for a while it seems like the session times out, and that causes Lucee to throw an error
from logs