>
> BigInsights Quality
> EGL C Block, 6th Floor
> IBM India Software Labs,
> Mail-Id : ashoj...@in.ibm.com
>
>
>
>
> - Original message -
> From: "Sandeep Moré" <moresand...@gmail.com>
> To: user@knox.apache.org
> Cc:
&g
Hi Sandeep,The knox version (0.12.0.2.6.2.0-205) I am using did not have this file ProxyInboundClient.java, is there a way I can put in somewhere in my verison ?
Thanks & Regards,Ashok Jose**BigInsights QualityEGL C Block, 6th FloorIBM
Hi Sandeep,
Is there a parameter that I can set the timeouts for both WebSocketServerConnection and WebSocketClientConnection to a larger value from the knox settings ? One of these is gateway.websocket.idle.timeout, is there an other one ?
Or are these set from the client program ?
Thanks
Hello Ashok,
This is interesting, Knox opens up two connections for Websockets, one on
the client side (browser/client etc.) and other on the backend (service
host).
The timeouts you are seeing are for the two
1. First debug line - WebSocketServerConnection - opens up websocket
connection to the
Hi Knox Experts,
Needed a help incase you are aware of this issue.
We have this scenario where in we are creating 20 python kernels concurrently, we see that of these around 6-7 kernels fail with "Exception: Remote host closed websocket" because of timeout.
When we tried the same testcase