Guidelines

[tgmweb]

Not an issue per se, but I did have some trouble getting this up and running, so I thought I'd jot it down for anyone else in a similar position.

1. If you are running Tomcat8, it already comes with the websocket.jar, so you have to remove it from the provided jar before you add it to your lib folder. See here: http://stackoverflow.com/questions/21852459/tomcat-7-0-50-java-webscoket-implementation-gives-404-error
2. If you are running nginx, you have to update your location information to add addition headers through to Lucee. See here: https://www.nginx.com/blog/websocket-nginx/

Hopefully that helps others.

Tom.

[sfeldkamp]

Do you mean:
delete javax.websocket-api-1.0.jar
from wsRailoEndpoint.jar
from railoWebSocketServer-1-0-0.zip
from the project releases page?

Because that's what I did and I'm still getting the 404 error. I did first install wsRailoEndpoint.jar without deleting javax.websocket-api-1.0.jar, but then I removed wsRailoEndpoint.jar, deleted the javax.websocket-api-1.0.jar, and replaced wsRailoEndpoint.jar in WEB-INF/lib.

Are jar files cached somewhere by Tomcat besides where they are installed? I stopped the server first and started it afterwards.

I'm pulling my hair out here. We have basically no other option for getting WebSockets going on Railo/Lucee.

[tgmweb]

Yes, that's what I had to do.

Also, make sure you're not running tuckey or something similar, as you'll need to add a rule to bypass that.

However, it was a while ago, and I gave up in the end as I couldn't find a way to relay the SessionID in the websocket to my app to send specific people messages. I was also running elasticbeanstalk which compounded my issues.

Sorry I can't help more...

[sfeldkamp]

It was a longshot, but I thought perhaps you meant deleting it from the tomcat lib websocket-api.jar.

Thank you for the quick reply and for the opened issue. I've at least identified the problem.

[quetwo]

@tgmweb : Sorry you couldn't figure out the SessionID. It should have come across the CONNECT message types on any watched channels. It should also come packaged with any message that the client sends to a watched channel as well. The sample WebsocketWatcherListner.cfc has a comment with the structure of how that should be able to be picked up.