I'm encountering this weird problem with one IIS Website / app:
The problem is that when i open a web browser on certain devices and access to the app, the FIRST and SECOND requests are EXTREMELY SLOW. It takes up to 30 seconds each to load.
After that everything runs smoothly.
This happens only after opening the web browser on CERTAIN devices.
I'll name the devices that the problem persist on and the ones that doesn't.
Devices with the problem:
Galaxy S 1 (cyanogen Mod 10)
Iphone 4S (stock)
ViewSonic VSD220 (runs android ICS)
Toshiba Laptop (win vista, i dont have the specs in hand)
Devices not showing the problem:
4 PC running win xp
Dell laptop (win 7, i dont have the specs in hand either)
The only common factor I've found is that the problem persist only with this APP on mobile devices.
In the laptop scenario i tried with both network cards (wired and wireless) and the results are the same.
I already tried with 2 different IIS servers and different versions (5.1 and 6.0). In different machines...
Creating a new the application pool on the 6.0 IIS server...
the APP pool recycle timer...
Also this is the only APP i have using .net framework 4.0
any suggestion or help would be really appreciated.
Based on our troubleshooting above, it's determined that some of the app's devices only have LAN connectivity and thus could not access external resources that were referenced in the app.
Related
While the app works perfectly in the DEBUG mode, most of the time, it hangs or shows Unresponsive Page error in chrome.
I haven't test it in other browsers because what I've written won't work in other browsers at all.
Unfortunately have no idea how I can monitor requests in IIS.
I should say that both Server App and Angular 4 App are hosted on the local IIS v10 with individual application pools.
I already used --enable-logging --v=1 --vmodule=metrics=2 command when starting google-chrome, but I guess nothing important are being saved in chrome_debug.log file or at least I can't read it.
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 am working on an ASP.NET application and I'd like the ability to test the application on my (Android) phone and iPad by connecting directly to my local IIS Express development server. I followed the instructions here on setting up IIS Express to allow remote connections. I am now able to view the application from another Windows machine on my local network by visiting http://my-computer-name:my-port-number/ in the browser. However, I am unable to view the application from any other platform (Android, iOS, and OS X - tested in both Chrome and Firefox); the browser silently churns away for a minute or so before giving me a generic "could not connect to my-computer-name:my-port-number" page.
What is the difference between the platforms that is disallowing me from viewing my ASP.NET application on non-Windows machines?
If your devices are on the same network, from the command prompt try ipconfig get the IP Address from your wireless and from your device try http://[IP Address]:[Port].
Like in this example:
http://192.168.2.122:5252
I am not an expert on Mac but if I recall correctly your issue may be associated with this:
http://www.wikihow.com/Add-a-Mac-to-a-Homegroup
What is the difference between the platforms that is disallowing me
from viewing my ASP.NET application on non-Windows machines?
The network to which they are connected. You seem to have mentioned that your Windows machine is connected to the same local network as the computer hosting the web application. But the other devices probably aren't. So make sure that those devices are connected to the same network.
I'm facing a problem when running the AdHoc distribution app, I've developed an application and test it using development certificate on real device, running successfully, but when produce the adHoc and send it to my client to test it, the application installed successfully but does not run, where is the problem in this case?
the application using large image file (about 3-5 MB each image, but the number of the image is small, about 5-6 image) how can it run on the development certificate ?
Solution:
It seems that the tested ad hoc device was using a 3.4 ios version, and the app was developed for ios 5 and was contain some feature of the ios 5, so it was crashing every time the app run.
thx in advance.
It seems that the tested ad hoc device was using a 3.4 ios version, and the app was developed for ios 5 and was contain some feature of the ios 5, so it was crashing every time the app run.
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