Websocket is closed after 15 minute

Jan 7, 2013 at 10:25 AM

Hi,

I am using superwebsocket,after connect the superwebsocket, if page is idle for 15 minute then socket closed automatically. how to extend this time. we need nearly 1 hour page may be in idle, after that we may send the message.

Jan 15, 2013 at 10:00 AM

Where did you host your SuperWebSocket?

If you host it in IIS, the life circle of SuperWebSocket server instance is same with the web site where it is running.

Jan 15, 2013 at 10:03 AM
Edited Jan 15, 2013 at 10:04 AM

Hi,

I have hosted as windows Service.

Jan 15, 2013 at 10:36 AM

Then you should check your clearIdleSession configuration.

http://supersocket.codeplex.com/wikipage?title=Basic%20configuration&referringTitle=Documentation

Jan 15, 2013 at 11:06 AM

Hi,

I have added following code in the configuration.

<server name="SuperWebSocket" serviceName="SuperWebSocket"   ip="Any" port="4502" mode="Async" idleSessionTimeOut="1200" keepAliveTime="1200">      </server>

but, still i am facing socket close issue in 15 minute.

 

 

Jan 15, 2013 at 12:14 PM
Is it host in a sever or in local pc?

Sent from my Windows Phone

From: mfdenni
Sent: 1/15/2013 7:06 PM
To: kerry-jiang@hotmail.com
Subject: Re: Websocket is closed after 15 minute [SuperWebSocket:428733]

From: mfdenni

Hi,

I have added following code in the configuration.

<server name="SuperWebSocket" serviceName="SuperWebSocket" ip="Any" port="4502" mode="Async" idleSessionTimeOut="1200" keepAliveTime="1200"> </server>

but, still i am facing socket close issue in 15 minute.

Jan 15, 2013 at 12:20 PM

It is hosted in amazon EC2 machine.(windows 2008 server).

Jan 15, 2013 at 2:58 PM

Could you do a test in your network environment? Some firewall will disconnect long connections no activity for a while.

Jan 27, 2014 at 11:23 PM
Hi,

In IIS Manager, please check also the settings of the Application Pool associated with your web site. Select the application pool, open "Advanced Settings" and set the proper value for the key "Idle Time-out (minutes)", usually 20 minutes. When the timeout expires, the idle worker process that handles your web site is shut down and so all the open sockets will close. You can set the value to 0 (never expires) and see if it works, even thought I would not advise.

Regards,

Walter