I have a .NET web application that's deployed to IIS6. Our users use IE8, and I've also been debugging this issue with FF 3.6.3. We have a report generation feature that can take a bit of time to complete, lately on average around 3.5 minutes. The problem is that while the report is generating on the server, at about the 2 minute 10 second mark, IE will redirect to "Internet Explorer cannot display the page". In FF, after the same amount of time, it's a blank white page.
While troubleshooting, I came across IIS's connection timeout property, which is 120 seconds by default. That seemed very close to 2 minutes 10 seconds, so I upped it to 5 minutes, but the browsers still redirected after 2 minutes 10 seconds. I then tried lowering the value to 10 seconds in IIS for the website (just to see what would happen), but still the browser redirected after 2 minutes 10 seconds. The connection timeout property does not seem to be doing anything at all, from what I can tell. I tried restarting the website, restarting the app pool, and even restarting IIS, with no change in my results.
My first question is what kind of result the user would see in their browser if IIS was actually enforcing the connection timeout. Would they see the "Internet Explorer cannot display the page" page, or something different?
I have also looked through my web.config for any values that might affect a timeout, but nothing stands out. I'm beginning to worry that there's a browser limit that's been set by group policy in the registry, but I can't be sure because the registry is locked down on end user machines.
Does anyone have any idea why IIS would not be enforcing that timeout limit? Am I looking in the wrong place, or is there another timeout value that could be causing this behavior, perhaps outside IIS completely? Any help would be much appreciated.
Yes, you would probably still see the "Internet Explorer cannot display the webpage" page.
The application has its own timeout value, the default being 110 seconds, according to this msdn topic. Try changing (or adding) the executionTimeout attribute of the httpRuntime element in the application's Web.config under <system.web>. If you don't have that element you'll have to add it. If you're using ADO.NET you'll also want to check your commandTimeout value in your DbCommand/SqlCommand object in your actual code.
Related
I developed a blazor server app which works fine on a desktop, and now i test her on the mobile platforms.
I met problem with the signalR connection when i put the browser in the background.
When i go back, if its enough fast, i have the message
"Attempting to reconnect to the server" x/8, and after it reconnect after maybe 15 seconds (which is too much), and if its like 5 minutes later im totally disconnected and i have to relaunch the app.
i found some documentation about that but nothing consistent. Because of blazor, the client configuration and event (in js) seem different than the classic signalr client, and for the server im beeing lost between the different timeout.
I try find a way to configure both server and client to manage a "sleeping" connection (ok if im disconnect after 20 minutes but i want at least be able to reconnect until 20 minutes of inactivity), but its really hard to test because im unable tu reproduce this behavior in development in my laptop.
I see some solution on internet who suggested make document.location.reload()
Blazor.defaultReconnectionHandler._reconnectCallback = function(d) {
document.location.reload();
}
But its not a solution for me as i don't want to lost everything in session.
thanks for your suggestion and help !
for those stuck into this same kind of problems, i was able to manage this by play with the signalr options described here : https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/signalr?view=aspnetcore-5.0&pivots=server
actually it was not really a mobile problems because i had the same kind of behavior by putting a laptop on sleep more than 3 minutes.
The 3 minutes expiration period was coming from this parameter
DisconnectedCircuitRetentionPeriod 3 minutes Maximum amount of time a disconnected circuit is held in memory before being torn down.
i just increase the time of this parameter and when the mobile/laptop go out of sleep it able to reconnect.
the blazor documentation is not really clear about that
I have a J2EE App and I've been running it for a couple of years...
recently there's chance that whatever page I want to visit, it may show up as just Plain HTML and may not be rendered...
No Logs are written about this behavior as if it's a normal thing...
usually I click to visit a page, the Browser shows some cue about sending the request to the server... I can check that everything works just fine back there... Now there's 2 ways I can see this error :
1. I wait and wait and wait... and the browser is still waiting for a response... If I lose patience and press F5, the page shows up as PlainText HTML.
2. I wait till the end and the Browser may or may not load the page... if it loads the page, it's only partial and some parts of the Javascript or HTML may not load at all.
Pressing F5 usually fixes the problem but after a while, this may happen again...
This used to happen with Tomcat 6.x every once in a while but became worse after using Tomcat 7.x .
at first I thought it's related to my App but then I noticed this pattern happening even in Tomcat's own Admin pages such as its Session Manager.
What can I do ? I'm using Tomcat 7.0.54. upgrading it to newer versions didn't help...
Thank you...
I have several MVC4 sites on my VPS. They all have the same issue. They are so slow (up to 10 seconds to load, which is not a good first impression).
I am aware that when you first load your site, it will take a little while due to various things I've read upon. I understand this.
The problem is the following situation is true.
Publish MVC4 site to server.
Load MVC4 site in browser a PC. Site takes a while to load but expected.
Look at other pages on the site. A few are slow, but generally all is OK.
Close the website.
Reopen the website.
All pages respond well.
Close the website.
Leave it idle for 1 hour.
Open website, it is slow again, as if it's only been published
I can only assume it's something to do with the session, IIS or the app pool
In webforms I used to have tracing, I don't appear to have that in MVC and I don't know how I can debug such an issue.
That's actually the expected behavior, given that after a period of inactivity the application pool will recycle, to free up unused resources. Check the application pool's Recycle settings to configure that duration.
If you also want additional control on what happens during recycling there are a few options:
IIS7.5 (ASP.NET 4) supports a feature called "AutoStart", which can warm up your site after deployment and after recycling.
IIS8 has additional support through the Application Initialization Module.
I am working on a project, the team (and vs2012) by default uses iis7.5 during development.
Very recently (yesterday) the sites I was debugging start loading very slow.
Using fiddler I could see that it would take about 30 seconds for every single call that is being made.
so "localhost:{port}" takes 30 seconds (2kb), once that finally comes back and the page starts to load it calls all the css and js files, each take about 30 seconds to load.
As this is a large application it quickly became unusable.
this happens whether I am debugging, or loading a page without debugging.
This same behavior happens an all sites on my dev machine, even plain newly build site exhibits the same behavior And occurs in all browsers.
I am able to "resolve" the problem several ways.
1. Switch from iis 7.5 to visual studio dev server.
(url does not change localhost:{port} to localhost:{port}.)
2. In web matrix, if I change the url from localhost:{port} to
http://{machinename}:{port} the site then runs faster (normal speed),
but debugging becomes and issue.
option 1 above does the trick and I dont seem to be effected too much by the change.
I am very curious as to why this is all of a sudden happening though, and would really like to fix the problem.
Any thoughts would be greatly appreciated.
I just upgraded my browser to Safari 4 and find that our website is having some major issues specific to that browser version. As I click through pages on our site it takes one or two clicks before the browser window simply goes blank. When the window goes blank, there is no source to view and no matter how many times I try to reload or if I try to load other pages of the site, I still get the blank window. It's as if the server takes the request and simply returns a blank page.
If I wait over 15 seconds and then hit refresh again, the page loads fine. Not sure why it starts working again... Maybe a cache issue???
It's a PHP site and I've tried turning on error_reporting(E_ALL);, but that doesn't give any information. I also tried putting an echo statement at the very beginning of the index.php file and verified that the page still goes blank without echoing that statement, so I'm thinking the problem is not php code specific. The Apache error log does not show any issues. I have the same site on my local development server and it doesn't have the problem.
Safari 4 is the only browser that shows this problem. Does anyone have any ideas how to debug/fix this?
My webserver is ubuntu Hardy running Apache 2 an Mysql 5.
We have an nginx load balancer in front of the apache server and I just figured out that Safari 4 requires the nginx keepalive_timeout setting to be 0. Took all day to figure that one out...
I've been having the same issue with Safari 4 on my site but found that when reloading pages that return blanks, the request never even makes it to the server. No entry shows up in Apache's logs.
The keepalive setting for your LB sounds like a direction I could sniff in. Not sure what leeway I will have though, being on shared hosting.
Mike
This looks to be a safari bug. We experience it too, and I have read other reports.
http://discussions.apple.com/thread.jspa?threadID=2064488&start=0&tstart=0