Hi Carl, This issue was just fixed for the upcoming 4.0.44 release:
async connections close after 5m regardless of WebSocketContext.setTimeout(): http://bugs.caucho.com/view.php?id=5841 -- Nam On 4/1/15 10:00 AM, resin-interest-requ...@caucho.com wrote: > Message: 1 > Date: Tue, 31 Mar 2015 18:01:51 +0100 > From: "c.whalley"<c.whal...@blueyonder.co.uk> > Subject: [Resin-interest] Set Resin webSocket timeout - the default is > too short > To:resin-interest@caucho.com > Message-ID:<551ad2ff.10...@blueyonder.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > Heres the solution for Jetty: > http://stackoverflow.com/questions/9056159/websocket-closing-connection-automatically > > I tried this in resin with no effect > > public class CustomWebSocketListener extends AbstractWebSocketListener { > ... > private WebSocketContext socketContext; > > @Override > public void onStart(WebSocketContext socketContext) throws > IOException { > // called when the connection starts > this.socketContext = socketContext; > socketContext.setTimeout(1 * 60 * 60 * 1000); > ... > > Whats the resin way please? > _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
