But I am facing this problem even without a proxy in between. The issue is occurring whenever communication is happening through TURN over TCP or UDP relay server. I have installed Kurento in docker and blocked all forward packets so that application is forced to use TURN installed in the same machine running over port 3478. What I am observing is that the websocket connection is breaking when the user interacts with Dashboard.
With Kind Regards Lalit Patel On Wed, Aug 19, 2020 at 11:58 AM Maxim Solodovnik <[email protected]> wrote: > Since OM works without Squid I would say you should tweak Squid > NOT OM > NOT Tomcat :)) > > On Wed, 19 Aug 2020 at 13:05, Lalit Patel <[email protected]> wrote: > > > > Hi Maxim, > > Could you please suggest how to do it ? The default buffer size > (org.apache.tomcat.websocket.binaryBufferSize, > org.apache.tomcat.websocket.textBufferSize) as per tomcat seems to be 8192 > bytes. Is it sufficient enough ? > > Ref- https://tomcat.apache.org/tomcat-9.0-doc/web-socket-howto.html > > > > Thanks and Regards > > Lalit Patel > > > > On Wed, Aug 19, 2020 at 9:54 AM Maxim Solodovnik <[email protected]> > wrote: > >> > >> Maybe you need to increase the limit for WebSocket message size? > >> drawing on WB can send big web-socket messages ... > >> > >> On Tue, 18 Aug 2020 at 22:38, Lalit Patel <[email protected]> wrote: > >> > > >> > Hi Maxim, > >> > I have observed that this error is not associated with Proxy. I am > facing this issue whenever media communication is happening through TURN > relay over TCP. Audio video is OK, users can see each other and everything > works fine as long as the user does not touch anything in dashboard. As > soon as the user interacts with the whiteboard or tries to upload some > file, all hell breaks loose and websocket connection breaks. It keeps on > breaking several times, even refreshing again. I am not able to find any > other reason except the websocket exception. Why is this happening, I have > no clue ? > >> > > >> > Thanks and Regards > >> > Lalit Patel > >> > > >> > On Fri, Aug 14, 2020 at 7:53 PM Maxim Solodovnik < > [email protected]> wrote: > >> >> > >> >> Unfortunately I can't help here > >> >> there are instructions for Nginx and Apache front end proxies > (please search mailing lists) > >> >> Maybe you can examine those and get some ideas? > >> >> > >> >> On Fri, 14 Aug 2020 at 17:13, Lalit Patel <[email protected]> > wrote: > >> >>> > >> >>> Hi, > >> >>> In our OMS deployment, we want to ensure that users even behind > strict firewall and proxy should be able to join. I am using a TURN server > to relay packets over TCP on port 443. I am planning to deploy TURN on a > separate machine. So in principle OMS will need minimum port 443 to run. I > deployed a squid proxy (Version 3.5.20) for testing. I am trying to > simulate a scenario where a user is connecting OMS through the proxy. > Connections are successful but with following issues- > >> >>> > >> >>> 1. It's not working with firefox due to the failure of WSS > connection. Not a problem, I can instruct users to use only the latest > Chrome browser. > >> >>> 2. In chrome browser, things run fine for a while but if user does > some activities like screen sharing, writing something on white board, WSS > connection breaks with following error in Catalina.out. Once this happens, > it keeps on happening for some time and then it stabilizes again till the > user does something again. > >> >>> a) WebSocketBehavior::closeHandler The client closed its > connection with code '1006' and message: 'error:140E0197:SSL > routines:SSL_shutdown:shutdown while in init' > >> >>> Error trace: > >> >>> > >> >>> An error occurred in web socket connection with id : 43 > >> >>> javax.net.ssl.SSLException: error:140E0197:SSL > routines:SSL_shutdown:shutdown while in init > >> >>> at org.apache.tomcat.util.net > .openssl.OpenSSLEngine.checkLastError(OpenSSLEngine.java:946) > >> >>> at org.apache.tomcat.util.net > .openssl.OpenSSLEngine.pendingReadableBytesInSSL(OpenSSLEngine.java:631) > >> >>> at org.apache.tomcat.util.net > .openssl.OpenSSLEngine.unwrap(OpenSSLEngine.java:558) > >> >>> at java.base/javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:634) > >> >>> at org.apache.tomcat.util.net > .SecureNioChannel.read(SecureNioChannel.java:617) > >> >>> at org.apache.tomcat.util.net > .NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1228) > >> >>> at org.apache.tomcat.util.net > .NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1203) > >> >>> at org.apache.tomcat.util.net > .NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1147) > >> >>> at > org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:72) > >> >>> at > org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171) > >> >>> at > org.apache.tomcat.websocket.server.WsFrameServer.notifyDataAvailable(WsFrameServer.java:151) > >> >>> at > org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:148) > >> >>> at > org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) > >> >>> at > org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:59) > >> >>> at > org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) > >> >>> at org.apache.tomcat.util.net > .NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1589) > >> >>> at org.apache.tomcat.util.net > .SocketProcessorBase.run(SocketProcessorBase.java:49) > >> >>> at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > >> >>> at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > >> >>> at > org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) > >> >>> at java.base/java.lang.Thread.run(Thread.java:834) > >> >>> > >> >>> b) WebSocketBehavior::closeHandler The client closed its > connection with code '1001' and message: 'null' > >> >>> > >> >>> In my opinion, these are some trivial issues which can be sorted > out, If anybody can suggest something to make it stable. > >> >>> > >> >>> Thanks and Regards > >> >>> Lalit Patel > >> >>> > >> >>> > >> >> > >> >> > >> >> -- > >> >> Best regards, > >> >> Maxim > >> > >> > >> > >> -- > >> Best regards, > >> Maxim > > > > -- > Best regards, > Maxim >
