Websockets timing out

2014-03-04 Thread Bob Mancarella
Tomcat 7.0.52 on Ubuntu 14.04 Websocket connection closes automatically after about 10 seconds. The browser creates the initial connection. OnOpen is called on the server. After 10 seconds OnClose is called and the connection is closed. I have tried changing connectionTimeout=-1 on Connector.

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
Ubuntu 13.04 and Tomcat 8 Same issue. Client makes the connection fine. Tomcat closes the connection in 10 seconds.

Re: Websockets timing out

2014-03-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bob, On 3/4/14, 1:15 PM, Bob Mancarella wrote: Ubuntu 13.04 and Tomcat 8 Same issue. Client makes the connection fine. Tomcat closes the connection in 10 seconds. What's the client timeout on the server side? Perhaps you are... timing out. -

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
Besides what I mentioned where would i find that? On Tue, Mar 4, 2014 at 1:54 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bob, On 3/4/14, 1:15 PM, Bob Mancarella wrote: Ubuntu 13.04 and Tomcat 8 Same issue. Client

Re: Websockets timing out

2014-03-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bob, On 3/4/14, 11:16 AM, Bob Mancarella wrote: Tomcat 7.0.52 on Ubuntu 14.04 Websocket connection closes automatically after about 10 seconds. The browser creates the initial connection. OnOpen is called on the server. After 10 seconds

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
Just using the EchoAnnotation code /// // client code

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
sorry, target is actually target = 'ws://' + window.location.host + '/inlook/websocket/echoAnnotationhttp://connect.ws/ ';

Re: Websockets timing out

2014-03-04 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Bob, On 3/4/14, 2:39 PM, Bob Mancarella wrote: Just using the EchoAnnotation code

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
More info. This is the return code to the browser 1006CLOSE_ABNORMAL*Reserved.* Used to indicate that a connection was closed abnormally (that is, with no close frame being sent) when a status code is expected. On Tue, Mar 4, 2014 at 2:41 PM, Bob Mancarella bobm...@gmail.com wrote: sorry,

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
Thats the strange thing. The code isnt doing anything. It connects, receives the onopen message and then the onclose with the 1006 return code within a few seconds. On Tue, Mar 4, 2014 at 3:04 PM, Bob Mancarella bobm...@gmail.com wrote: More info. This is the return code to the browser

Re: Websockets timing out

2014-03-04 Thread Mark Thomas
On 04/03/2014 16:16, Bob Mancarella wrote: Tomcat 7.0.52 on Ubuntu 14.04 Websocket connection closes automatically after about 10 seconds. The browser creates the initial connection. OnOpen is called on the server. After 10 seconds OnClose is called and the connection is closed. I have

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
JSR356

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
OK, this is strange. If I go here http://www.websocket.org/echo.html I get the same results. Click on Connect but don't hit Send and I get a Disconnected message soon after. If I use TLS it seems to work. If I hit Send immediately after Connect it seems to work. Anyone else seeing this? On

Re: Websockets timing out

2014-03-04 Thread Mark Thomas
On 04/03/2014 20:36, Bob Mancarella wrote: OK, this is strange. If I go here http://www.websocket.org/echo.html I get the same results. Click on Connect but don't hit Send and I get a Disconnected message soon after. If I use TLS it seems to work. If I hit Send immediately after Connect it

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
could you try this. http://dev.bizunite.com/inlook/echo.html click on annotation API then Connect and see if you stay connected. On Tue, Mar 4, 2014 at 3:44 PM, Mark Thomas ma...@apache.org wrote: On 04/03/2014 20:36, Bob Mancarella wrote: OK, this is strange. If I go here

Re: Websockets timing out

2014-03-04 Thread David kerber
On 3/4/2014 3:46 PM, Bob Mancarella wrote: could you try this. http://dev.bizunite.com/inlook/echo.html click on annotation API then Connect and see if you stay connected. Seems to be working fine for me. On Tue, Mar 4, 2014 at 3:44 PM, Mark Thomas ma...@apache.org wrote: On 04/03/2014

Re: Websockets timing out

2014-03-04 Thread Mark Thomas
On 04/03/2014 20:50, David kerber wrote: On 3/4/2014 3:46 PM, Bob Mancarella wrote: could you try this. http://dev.bizunite.com/inlook/echo.html click on annotation API then Connect and see if you stay connected. Seems to be working fine for me. I get an immediate close with the

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
Ugh. Looks like I need to use wss in my environment. I just found this. If an encrypted WebSocket Secure connection (wss://) is used, then in the case of transparent proxy servers, the browser is unaware of the proxy server, so no HTTPCONNECT is sent. However, since the wire traffic is encrypted,

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
I didn't implement programmatic. On Tue, Mar 4, 2014 at 3:52 PM, Mark Thomas ma...@apache.org wrote: On 04/03/2014 20:50, David kerber wrote: On 3/4/2014 3:46 PM, Bob Mancarella wrote: could you try this. http://dev.bizunite.com/inlook/echo.html click on annotation API then Connect