Igal Sapir

There might be a `deploy` log but I'm not sure without checking. I'll have to test it myself when I have a moment.

I'll look into it. Thanks.

Please try `2.0.3` -- it's the same code as `2.0.2` but packaged a bit differently and should resolve this issue.

> Where can we find "servlet-filter-utils-1.1.1.jar"? @psarin Is that for initializing the Session object? You can use net.twentyonesolutions.servlet.listener.HttpSessionInitializer which comes with the WebSocket extension. See https://github.com/isapir/lucee-websocket/blob/master/src/main/java/net/twentyonesolutions/servlet/listener/HttpSessionInitializer.java#L11

This error comes from the servlet container (Tomcat) and is part of the Java specification IIRC. Why do you need to call this function multiple times? In general, you should...

Do your Listener methods have the code wrapped in a try/catch? I'd add that if no, and log all errors. Usually if you get an error from the server it's...

If it's in the Listener or your Application then the regular Lucee logs (e.g. application.log, exception.log, etc.); If low level issue then Tomcat logs. I'd check all.

Do you have more information on this issue? Anything from the logs?

IIRC something has changed in Tomcat that is causing that error. It was working fine in Tomcat 8.5.35 and probably there equivalent 9.0.x version. I hadn't had time to look...

Do you mean that for sharing Session information, or balancing the actual WebSocket connections? Can you be more specific on what you request?