Closed sfeldkamp closed 8 years ago
It looks like the WebSocket engine (wsRailoEndpoint) isn't getting instantiated. It should grab onto anything that is within /wsEndpoint/, based on the Java annotations compiled into the class.
This leverages the javax.websocket package within Tomcat, so you shouldn't need to load that.
One thing to try is to flip the metadata-complete="true" in the WEB-INF/web.xml file to false. This will force Tomcat to scan the entire project and it should pick up on the annotations to load the library. If that works, then you will need to figure out why the wsEndpointLoader isn't actually executing. If it dosen't, then it is possible that something is causing either the JAR not to be loaded, or it not not being scanned.
Success! The problem was a mislocation of the
We've decided instead to install the
It will take over for all the domains at the /wsEndpoint/* locations, but if that doesn't bother you, then it's not a big deal. I know of one site that does it this way on purpose. The channel watchers on the websocket side will be global however.
Environment details: Lucee 4.5.1.022 Tomcat 8.0.24.0 JVM 1.7.0_79-b14 OS: Linux
When trying to connect to my server I get the following error returned to the browser (as output by Chrome Devtools). Yes, 8001 is the port that my Lucee installation is configured to serve from and I am able to successfully browse the site on that port.
This error is written into the exception.log from that request.
It appears that Tomcat is trying to serve the page index.cfm in my channel, which of course does not exist. Maybe the request is not being intercepted properly by the servlet engine? I have added the following to the web.xml file in WEB-INF.
This is the same error that is reported if you don't remove the javax.websocket-api-1.0.jar from the wsRailoEndpoint.jar when deploying to Tomcat8, however I have removed that jar. I don't believe I'm getting a conflict on javax.websocket package now.