IIS7 Require Restart

Mar 8, 2012 at 11:34 AM

I am facing an issue that after few minutes Application is Superwebsocket is unable to Open Connection until i restart IIS or Recycle the Application Pool.

I am using SuperWebsocket latest version in Windows 7 environment (IIS 7.5). 

Coordinator
Mar 8, 2012 at 12:00 PM
Did you check the log of SuperWebSocket?

Sent from my Windows Phone

From: dhafaiz
Sent: 3/8/2012 7:34 PM
To: kerry-jiang@hotmail.com
Subject: IIS7 Require Restart [SuperWebSocket:347802]

From: dhafaiz

I am facing an issue that after few minutes Application is Superwebsocket is unable to Open Connection until i restart IIS or Recycle the Application Pool.

I am using SuperWebsocket latest version in Windows 7 environment (IIS 7.5).

Mar 8, 2012 at 1:54 PM

There is no Log in WorkingDir/ Log Folder, Do i need to Enable it From Some Where ... My Web.config Setting are



	
		
			
			
			<!--<server name="SecureSuperWebSocket" serviceName="SuperWebSocket" ip="Any" port="815" mode="Sync" security="tls">
				--><!--Please install the certificate to your trusted certificates store, the password is 'supersocket'--><!--
				<certificate filePath="localhost.pfx" password="supersocket" isEnabled="true"></certificate>
			</server>-->
		
		
			
		
	
Coordinator
Mar 8, 2012 at 1:58 PM

No log?

The logs should be stored in WorkingDir/Logs.

Do you have log4net.config file in WokringDir/Config? The line LogUtil.Setup() also required if you want to enable logging.

Mar 12, 2012 at 3:30 PM

I had made idlesessionmode = true and when there is no activity for 300 seconds which is default time , it worked well for 3 attempts but after after 3 attempts when application tries to connect it  doesn't, i checked every property and everything seems ok  but unable to connect until i refreshes page and sometimes i need to restart IIS.

Kindly tell me which property or method should given me the status or  error of connection moreover i had used enterprise library for application logging .

Coordinator
Mar 12, 2012 at 3:54 PM

Do you have log4net.config in /Config folder?

Mar 13, 2012 at 9:53 AM

Kindly find the status of Log folder.

debug.Txt

2012-03-13 13:18:28,237 [4400] DEBUG SuperSocket - SubProtocol Basic found the commands below:

err.TXT

Empty

info.txt

2012-03-13 13:18:28,284 [4400] INFO  SuperSocket - SuperWebSocket has been started
2012-03-13 13:18:31,526 [1028] INFO  SuperWebSocket - Session: dce31a50-2f0a-43a8-8fa6-cf01374d5551/127.0.0.1:51327
New SocketSession was accepted!
2012-03-13 13:18:32,271 [1028] INFO  SuperWebSocket - Session: d1cb0bb7-1cec-466b-815c-ac165c6809cd/127.0.0.1:51328
New SocketSession was accepted!
2012-03-13 13:18:37,276 [2204] INFO  SuperWebSocket - Session: d1cb0bb7-1cec-466b-815c-ac165c6809cd/127.0.0.1:51328
This session was closed!
2012-03-13 13:39:28,469 [4984] INFO  SuperWebSocket - Session: dce31a50-2f0a-43a8-8fa6-cf01374d5551/127.0.0.1:51327
This session was closed!
2012-03-13 13:39:28,469 [4400] INFO  SuperSocket - SuperWebSocket has been stopped
2012-03-13 13:39:28,474 [2204] INFO  SuperSocket - SuperWebSocket has been stopped

perf.txt

2012-03-13 13:19:28,297 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 34M, Virtual Memory Usage: 364M, Total Thread Count: 24
2012-03-13 13:19:28,298 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:19:28,300 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0.0166314634024648/s
2012-03-13 13:20:28,301 SuperSocket - CPU Usage: 49.95%, Physical Memory Usage: 34M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:20:28,302 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:20:28,302 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:21:28,311 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 34M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:21:28,312 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:21:28,312 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:22:28,322 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 34M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:22:28,322 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 13:22:28,323 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:23:28,331 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 34M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:23:28,331 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:23:28,332 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:24:28,343 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 34M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:24:28,343 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:24:28,343 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:25:28,353 SuperSocket - CPU Usage: 48.46%, Physical Memory Usage: 34M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:25:28,353 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:25:28,353 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:26:28,363 SuperSocket - CPU Usage: 48.56%, Physical Memory Usage: 34M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:26:28,363 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:26:28,363 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:27:28,373 SuperSocket - CPU Usage: 47.69%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:27:28,373 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:27:28,373 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:28:28,382 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:28:28,383 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:28:28,383 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:29:28,393 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 35M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:29:28,393 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:29:28,393 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:30:28,402 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 35M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:30:28,403 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:30:28,403 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:31:28,413 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:31:28,413 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:31:28,414 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:32:28,428 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:32:28,428 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:32:28,428 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:33:28,433 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:33:28,433 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:33:28,433 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:34:28,443 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:34:28,443 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:34:28,443 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:35:28,453 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:35:28,453 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:35:28,454 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:36:28,464 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:36:28,464 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 13:36:28,464 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:37:28,473 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:37:28,473 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:37:28,474 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:38:28,485 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:38:28,485 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:38:28,485 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s

Mar 13, 2012 at 11:06 AM

After i applied clearIdleSession="true" following is the result , after 14:09 no activities are recorded in logs by SuperWebSocket.

info.txt

2012-03-13 13:48:53,032 [4124] INFO  SuperSocket - SuperWebSocket has been started
2012-03-13 13:48:55,938 [4724] INFO  SuperWebSocket - Session: a4669a5c-3a05-457d-9ea3-38d1420e7bdc/127.0.0.1:55052
New SocketSession was accepted!
2012-03-13 13:54:53,045 [2412] INFO  SuperWebSocket - Session: a4669a5c-3a05-457d-9ea3-38d1420e7bdc/127.0.0.1:55052
The socket session has been closed for 357.056 timeout, last active time: 3/13/2012 1:48:55 PM!
2012-03-13 13:54:53,085 [2412] INFO  SuperWebSocket - Session: a4669a5c-3a05-457d-9ea3-38d1420e7bdc/127.0.0.1:55052
This session was closed!
2012-03-13 13:54:53,093 [4904] INFO  SuperWebSocket - Session: 76254edd-8545-4a47-a3c7-fbe23c6f1133/127.0.0.1:55059
New SocketSession was accepted!
2012-03-13 14:00:53,057 [2412] INFO  SuperWebSocket - Session: 76254edd-8545-4a47-a3c7-fbe23c6f1133/127.0.0.1:55059
The socket session has been closed for 359.963 timeout, last active time: 3/13/2012 1:54:53 PM!
2012-03-13 14:00:53,059 [2412] INFO  SuperWebSocket - Session: 76254edd-8545-4a47-a3c7-fbe23c6f1133/127.0.0.1:55059
This session was closed!
2012-03-13 14:00:53,063 [4904] INFO  SuperWebSocket - Session: 1ee64e0b-a691-4afd-a6cf-f86b4c1879c7/127.0.0.1:55129
New SocketSession was accepted!
2012-03-13 14:06:53,071 [2412] INFO  SuperWebSocket - Session: 1ee64e0b-a691-4afd-a6cf-f86b4c1879c7/127.0.0.1:55129
The socket session has been closed for 360.006 timeout, last active time: 3/13/2012 2:00:53 PM!
2012-03-13 14:06:53,073 [2412] INFO  SuperWebSocket - Session: 1ee64e0b-a691-4afd-a6cf-f86b4c1879c7/127.0.0.1:55129
This session was closed!
2012-03-13 14:06:53,077 [4904] INFO  SuperWebSocket - Session: a8bd5f6a-0bed-48b8-bc18-df5ca1792fb5/127.0.0.1:55184
New SocketSession was accepted!
2012-03-13 14:09:38,727 [1908] INFO  SuperWebSocket - Session: a8bd5f6a-0bed-48b8-bc18-df5ca1792fb5/127.0.0.1:55184
This session was closed!
2012-03-13 14:09:38,729 [4124] INFO  SuperSocket - SuperWebSocket has been stopped
2012-03-13 14:09:38,729 [2412] INFO  SuperSocket - SuperWebSocket has been stopped

perf.txt

2012-03-13 13:49:53,047 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 34M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:49:53,047 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:49:53,050 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0.0166309102097158/s
2012-03-13 13:50:53,063 SuperSocket - CPU Usage: 49.37%, Physical Memory Usage: 34M, Virtual Memory Usage: 363M, Total Thread Count: 22
2012-03-13 13:50:53,063 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 13:50:53,063 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:51:53,060 SuperSocket - CPU Usage: 49.95%, Physical Memory Usage: 34M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 13:51:53,060 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:51:53,061 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:52:53,070 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 34M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:52:53,070 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:52:53,070 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:53:53,080 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 13:53:53,080 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:53:53,081 SuperWebSocket - Total connections: 1, total handled commands: 1, command handling speed: 0/s
2012-03-13 13:54:53,091 SuperSocket - CPU Usage: 48.51%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 13:54:53,091 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:54:53,091 SuperWebSocket - Total connections: 0, total handled commands: 2, command handling speed: 0.0166636116711936/s
2012-03-13 13:55:53,101 SuperSocket - CPU Usage: 49.23%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 13:55:53,101 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:55:53,101 SuperWebSocket - Total connections: 1, total handled commands: 3, command handling speed: 0.0166638893517747/s
2012-03-13 13:56:53,112 SuperSocket - CPU Usage: 49.95%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 13:56:53,112 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:56:53,112 SuperWebSocket - Total connections: 1, total handled commands: 3, command handling speed: 0/s
2012-03-13 13:57:53,120 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 13:57:53,120 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:57:53,121 SuperWebSocket - Total connections: 1, total handled commands: 3, command handling speed: 0/s
2012-03-13 13:58:53,130 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 13:58:53,130 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 13:58:53,131 SuperWebSocket - Total connections: 1, total handled commands: 3, command handling speed: 0/s
2012-03-13 13:59:53,142 SuperSocket - CPU Usage: 49.51%, Physical Memory Usage: 35M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 13:59:53,142 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 13:59:53,143 SuperWebSocket - Total connections: 1, total handled commands: 3, command handling speed: 0/s
2012-03-13 14:00:53,151 SuperSocket - CPU Usage: 49.23%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 14:00:53,151 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 14:00:53,152 SuperWebSocket - Total connections: 1, total handled commands: 5, command handling speed: 0.0333277787035494/s
2012-03-13 14:01:53,161 SuperSocket - CPU Usage: 49.23%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 14:01:53,162 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 14:01:53,162 SuperWebSocket - Total connections: 1, total handled commands: 5, command handling speed: 0/s
2012-03-13 14:02:53,173 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 14:02:53,174 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 14:02:53,174 SuperWebSocket - Total connections: 1, total handled commands: 5, command handling speed: 0/s
2012-03-13 14:03:53,181 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 14:03:53,186 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 14:03:53,186 SuperWebSocket - Total connections: 1, total handled commands: 5, command handling speed: 0/s
2012-03-13 14:04:53,191 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 14:04:53,191 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 14:04:53,191 SuperWebSocket - Total connections: 1, total handled commands: 5, command handling speed: 0/s
2012-03-13 14:05:53,202 SuperSocket - CPU Usage: 48.46%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 14:05:53,203 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 14:05:53,203 SuperWebSocket - Total connections: 1, total handled commands: 5, command handling speed: 0/s
2012-03-13 14:06:53,212 SuperSocket - CPU Usage: 49.90%, Physical Memory Usage: 36M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 14:06:53,213 SuperSocket - AvailableWorkingThreads: 199, AvailableCompletionPortThreads: 200
2012-03-13 14:06:53,213 SuperWebSocket - Total connections: 1, total handled commands: 7, command handling speed: 0.0333277787035494/s
2012-03-13 14:07:53,222 SuperSocket - CPU Usage: 46.92%, Physical Memory Usage: 37M, Virtual Memory Usage: 364M, Total Thread Count: 23
2012-03-13 14:07:53,222 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 14:07:53,223 SuperWebSocket - Total connections: 1, total handled commands: 7, command handling speed: 0/s
2012-03-13 14:08:53,233 SuperSocket - CPU Usage: 50.00%, Physical Memory Usage: 37M, Virtual Memory Usage: 364M, Total Thread Count: 22
2012-03-13 14:08:53,233 SuperSocket - AvailableWorkingThreads: 198, AvailableCompletionPortThreads: 200
2012-03-13 14:08:53,234 SuperWebSocket - Total connections: 1, total handled commands: 7, command handling speed: 0/s

Coordinator
Mar 13, 2012 at 2:19 PM

It seems that you websocket server was stopped by the application pool of the hosting website. Because if there is no requests for a longer time, the site would be unloaded. If you don't know how to control it, you'd better host your websocket server in a windows service.

Mar 13, 2012 at 3:01 PM

Query 1:- Is there any way By which i can get the get the status of Server and Restart SuperWebSocket Server other than start() method.

Query 2:- When i restart IIS, Client Sessions are also Lost , is there any work around for this.

Basically going to Windows Service will require alot of development and QA so i am trying to fix this issue without windows service.

Coordinator
Mar 13, 2012 at 3:28 PM

Do you know more about the asp.net website application mode? What's the the client you are using? I think if you are using a webpage as websocket client and the page is hosted in the same site with the SuperWebSocket, then although the site was shutdown because of no requrest for a long time, but if the webpage is being visit, the SuperWebSocket server instance would be started automatically at the same time.

Could you verify this point with my sample project SuperWebSocketWeb?

You also can debug the site's starting and stopping behavior by set a break point in Global.asax.cs.

Mar 14, 2012 at 8:50 AM

My Client is using WebSocket4Net and its a Windows Application, ok i thing i should move now to Windows Service.

Can you give me idea of How My Web Application will send messages to Windows Service as , SuperWebSocket Server will be Running in Windows Service.

Coordinator
Mar 14, 2012 at 8:58 AM

I think you can use WebSocket4Net in webapplication to connect the websocket server!

Mar 14, 2012 at 11:27 AM

i am now confused ... kindly share some code or link. 

i am now implementing windows service which will host superwebsocket server. .

how client which is on other location will connect to my superwebsocket server and send messages.

secondly how my web application will  connect to my superwebsocket server and send messages.

Coordinator
Mar 14, 2012 at 2:15 PM

SuperWebSocket already provided windows service hosting application named "SuperWebSocketService".

The client code is extremely easy, the demo code is shown on the homepage of WebSocket4Net.