WebSockets in the wild

martin · November 6, 2019, 10:01am

Hi,

I have spent some time looking at using WebSockets with Lucee via the websocket extension.

It took me a while to get this working. It looks like it will not work with commandbox, so I set it up on a windows machine using IIS. This post helped greatly with this:
https://lucee.daemonite.io/t/troubleshooting-lucee-websockets-with-iis-and-arr/2687/3

I have come up against a few quirky issues so far with WebsocketRegister() where it kills the websocket if it is called more than once:

github.com/isapir/lucee-websocket

Multiple Endpoints may not be deployed to the same path

opened 12:12AM - 24 Aug 17 UTC

redtopia

I'm getting the following error in websocket.log when calling WebsocketRegister(…) after this function has already been called. ` DEBUG","http-nio-8888-exec-6","08/23/2017","17:57:53","myapp","Failed to register endpoint /ws/messages/thread/{channel}: Multiple Endpoints may not be deployed to the same path [/ws/messages/thread/{channel}] : existing endpoint was class net.twentyonesolutions.lucee.websocket.LuceeEndpoint and new endpoint is class net.twentyonesolutions.lucee.websocket.LuceeEndpoint ` When this happens, my websockets are failing in the browser during the onHandshake phase with a 500 error. I do not see any other error information in the logs. To fix this, I have to restart Lucee. Would it make sense to have another function that can be called that will cleanup and close all websockets on the server?

I was wondering if anybody is actually using this on a production site? If so, do they have any advice or things to look out for before I go to far down this path…???

Are there any alternatives to this extension? I have not been able to find anything obvious, but was not sure if there some Java that could be used for this?

Thanks,

Martin

Redtopia · December 12, 2019, 8:54pm

I am using it on production, but I have to say that it does not work very well. My webhooks run polls when the webhook connections can’t be established, so I’m not relying on them to work 100% of the time. @isapir is aware of the issues and I think it’s best to work with him on it directly through the github page for the extension. My guess is that the issues would be relatively easy to fix and all that is needed is some $$ to pay him to dig into it. You could also look at 3rd party, external web hook solutions like the AWS API gateway. Amazon API Gateway | API Management | Amazon Web Services, and there are others.

martin · December 16, 2019, 2:24pm

@Redtopia Thanks for the insight.

bdw429s · August 26, 2022, 8:15pm

6 posts were split to a new topic: Websocket extension and CommandBox