Websockets do not start on Server Reboot

dev
1

When I restart the Server, Lucee websockets do not work until I restart Lucee.

Lucee version: 7.1.0.204 (was happening in previous versions)
Websocket: 3.0.0.20-SNAPSHOT

2

Thanks for reporting this — I’ve logged it as LDEV-6456: Jira

The fact that a manual Lucee restart fixes it but an OS reboot doesn’t points to a startup ordering/timing issue in how the WebSocket listener initializes on a cold boot. To help narrow it down, could you share:

  • How Lucee starts on boot (systemd/service, Tomcat, Docker, etc.)?
  • Anything in the logs at boot time (out/err logs and the WebSocket extension log) around when the listener would come up?
  • Whether the WebSocket port is bound at all after a reboot (e.g. netstat/ss), or bound but unresponsive?

Please follow LDEV-6456 for updates.

3

I am using Rocky 9 linux with Virtualmin/Webmin. Lucee is installed with the Lucee installer, which packages its own Tomcat.

I have noted this problem in this post: Websocket Extention 3.0.0.18 on Lucee 7 does not seem to work - #5 by MiniFireDragon

Which has a copy of the log. If you need more, I will reboot the webserver and get the websocket log again, but the error was the same.