I had a signlar app that ran on my windows 10 pro box. I used IIS on it and it allowed me to have 10 concurrent connections.
But now I needed to expand my concurrent connections to my app. So I purchased some new hardware and Windows Server Essentials 2012.
I just setup my signlar app and started opening up browser windows to test it on the new box and I couldn't get more than 4 connections open at once. The fifth browser page just hangs. as soon as I close another browser page the hanging page appears.
I'm completely stumped.
Related
I ran into problems developing an application (.Net Framework 4.7+) using SignalR (v. 2.2). My IIS (v. 10 on Windows 10 HOME) is hanging after 2 established connections. It hangs completely, so no other site, hosted there, is no longer available.
I trieid to reproduce it on sample project (SignalR Chat). I downloaded it from https://learn.microsoft.com/en-us/aspnet/signalr/overview/getting-started/tutorial-getting-started-with-signalr-and-mvc (http://code.msdn.microsoft.com/Getting-Started-with-c366b2f3). Hosted it in IIS. IIS hangs after 2 established connections (2 tab opened, on third tab page opens from cache, but message isn't posted, if force refresh with CTRL+F5, then page not loading at all). I updated the sapmple project to the latest versions of SignalR and OWIN. Same result.
Ok. I took a clean system (Windows 10 PRO), installed IIS there, hosted sample project there. Instead of 2 connections it hangs after 9 websocket connections. I tried to change the transport to LongPolling, and server hangs after 6 connections. Here is noted that on client OS (like WIndows 10) there is a limitation to 10 simultaneous connections. But not 2. Using IISExpress there are no such restrictions.
Checked this question. But there is no CPU usage at all. I tried all the solutions proposed here. No result.
2 simultaneous is extremely low.
It's because you're using a non server version of IIS. Deploy it to a server and it'll be fine.
Similar questions and answers: SignalR: worker process is limited to 10 concurrent requests
I just started using SignalR (latest 2.0.3) on project running latest IIS and Visual Studio 2013.
I noticed an issue where sometimes the web page just hangs trying to load for an abnormal amount of time (never actually loads).
When this happens, I go into Visual Studio and hit the square to stop debugging, and visual studio starts to hang (not that it freezes VS but just loading symbol trying to stop debugging never actually stops debugging)
I realized the solution is to stop IIS which immediately causes the page to load and visual studio to respond and stop debugging. Start IIS and it's back to normal but this has occured multiple times already.
When this happens, try checking the current requests in IIS (go to Worker Processes in the IIS server features view and double-click the App Pool of your website) and I suspect you'll find 10 of them in process. This can happen because IIS on Win7/Win8 is limited to 10 concurrent requests and depending on your app, signalR could be using all of them up. and once all of those requests are used up, new requests will hang.
You can also kill them requests by recycling the App Pool.
I have an ASP-based application which provides real-time data from a local server to a small group of local users via mobile and desktop browsers (around 10 at any one time). Most of my installations use IIS running on Windows 7 Pro. Until now I have been using ajax short polling but am now prototyping changing the transport to SignalR.
Unfortunately it seems that using IIS on Windows 7 is not an option with since SignalR keeps a large number of connections open and in this configuration IIS has a concurrent connection limit of 10:
http://www.asp.net/signalr/overview/signalr-20/getting-started-with-signalr-20/supported-platforms
I am considering attempting to use IIS Express for my deployments. Is this a route worth pursuing? What are the pitfalls? Do I have any other options (other than to install Windows Server).
Thanks all
You can use self host signalR on a windows service see here for a sample
I use it on a Win7 machine
Occasionally when I reboot one of the servers at a client site the Web Apps running in IIS do not automatically start backup when the server is done rebooting. The IIS service starts up just fine, its set to Auto Start and there are no errors in the event log. Just none of the Web Apps are running, I have to click each one and click start. This only happens occasionally, as they usually start but its completely baffling.
Any thoughts? Its a mix of Classic ASP and ASP.NET applications. There are a total of 4 application pools running between around 8 web applications.
I have seen this happen when apps rely on a resource that is not yet available to the server, such as a network share.
Some people combat this problem by writing a Windows Service who's job is to check for such conditions and start the application.
I'm running a 32-bit asp.net app on iis6 on windows server 2003 (64-bit) and am encountering the following problems:
App takes 15-20 seconds to spin up.
App works quickly for a bit.
Something happens - maybe a recompile? The app takes 15-20 seconds to spin up again.
Nothing odd in Event Viewer or IIS logs- page eventually gets served up with a 200. Security log shows NETWORK SERVICE calling IUSR "success."
Also running filezilla server and Symantec Endpoint Protection.
Any ideas how to further trace this or what to check in my configuration?
The application isn't restarting- it seems to start fine and then take requests from one of my browsers. When I switch to another browser and start trying to access the site, it hangs for a couple of minutes.
I logged application-start in global.asax.cs and it starts fine - and quickly.
Have you checked that the application pool allows 32 bit application? In advanced box of application pool there are a setting to allow this.
Check this screendump, with the standard setting for 64 bit machine (false) enabled.
http://tinyurl.com/3jcr9mw
Not the issue - it's been set properly to 32-bit mode. Unsolved