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 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 > >>

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
ber 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. > > &g

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 wrote: > On 04/03/2014 20:36, Bob Mancarella wrote: > > OK, this is strange. If I go here http://www.webs

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
n Tue, Mar 4, 2014 at 3:22 PM, Bob Mancarella wrote: > JSR356 >

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
JSR356

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 wrote: > More info. > This is the return code to the b

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 wrote: > sorry, target is actua

Re: Websockets timing out

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

Re: Websockets timing out

2014-03-04 Thread Bob Mancarella
ot;echoTextMessage: " + msg); } @OnClose public void onClose(Session session) { System.out.println("Close connection for client"); } @OnError public void onError(Throwable exception, Session session) { System.out.println("Error for client"); } } On Tue, Mar 4, 2014 at 2:29 PM

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 1

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.

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. Al