I am using Application Insight for Web Pages(Javascript) and seen that for a particular resource it logs errors constantly because of some extension of the browser. How to avoid such exception caused by another plugins/extension creating load on my server. However, we can't disable(or ask to disable) the extension as its equally important for us.
if anyone out there has encountered this earlier or know the way to avoid exceptions to be tracked which are caused by external plugins.
Related
I'm using Angular with angular/fire and having issues with the Performance Module.
Our application needs to work within an Iframe (part of a business strategy we have not been able to change yet).
When a user visits the website hosting the Iframe from Safari the application crashes with a SecurityError.
Unhandled Promise rejection: IDBFactory.open() called in an invalid security context
I've tried dynamically importing the AngularPerformaneModule only once I've detected that we were in an environment where IDBFactory worked.
I've tried switching out all of IDBFactory with a fake using fake-indexeddb.
So far, neither of those solutions have worked.
If anyone has any ideas as to how to handle this situation it would be much appreciated.
For the solution, it's acceptable for the performance module to not operate within an Iframe (or when the IDBFactory is not available). There are other contexts when gathering metrics is possible that I can count on.
Since we moved the majority of our users to our asp.net web application running as a web application in Azure we've experienced an intermittent issue where the application will crash for all users, responding only with time-outs or 502/503 errors. This is usually occurring after we've made a configuration change (like changing an app setting in the portal) or swapping slots during a deployment. The very frustrating thing is that there appears to be no way to get it back until it eventually sorts itself out. During and immediately before the outage the diagnostics look fine - minimal CPU and memory usage. Lots of errors but they're most timeout errors. This problem is not resolve by scaling out or up, application restarts have no effect. Even killing the w3wp does not bring the app back. CPU profiles taken during outage show failed requests but not much else.
Does anyone know what might be going on here or have any ideas of what we could try?
While running Customer’s .NET processes in Azure Web App environment, it may intermittently crashes due to code or performance issues. It’s important to capture the crash dump when such crash/exception happen automatically for further investigation.
Here is a CrashDiag Site Extension, which can easily help us to capture the necessary data when intermittent unhandled exception happens. To capture dump for exceptions, you could refer to this article.
And as you have said, you only get error message with timeout or 502/503, here is an article you could refer to troubleshoot it.
This issue was actually being caused by our ORM writing to the TraceWriter. A configuration flag had been left on in the production environment due to a change in the deployment process. The TraceWriter is thread safe so was creating locks and blocking the CPU. Busy usage periods would cause requests to the TraceWriter to start queuing, thus leading to a non-responsive application.
We are hosting our website in Azure. During the deployment(TFS) we will do the below Steps as the part of the deployment pipeline.
Stop the WebApp
Deploy Web App Service
Start the WebApp
After the 1st step, if anyone tries to access our website, then by default Azure will return the below page
We really don't want our users to show this page during the outage. We are planning to show our own outage image/page in such case.
Is there is any way to achieve this?
Since Azure Web Apps in a Paas model, I'm wondering how to do this?
Any inputs Appreciated!
It seems that it does not suppport custom error page at this time. There is feedback on Enabling users to create custom error pages for 403 and 503 service unavailable messages.
I think you could up vote to promote the realization of this feature.
Putting some additional information regarding the solution for my own question here,
Just found the OP in SO where the feedback originated
There are two categories of HTTP errors that can happen on Azure Web
Apps:
Those that happen in IIS on the Web Worker where your site is running.
Those that happen before it reaches that. This includes cases when the
site is stopped, in the process of restarting, or potentially affected
by some other issue in the system. One way to tell if an error is #1
or #2 is to turn on http logging, and see if it gets logged. Only #1
will.
For #1, you can customize errors using standard techniques. But for For #2, there is currently no way for you to customize the pages returned by Azure.
Thanks, #David Ebbo and #SamJolly
We have a Flex Air application that calls web services that sometimes give us this error:
Unable to load WSDL. If currently online, please verify the URI and/or format of the WSDL
It's more frequent on OS X, but it does happen on Windows as well. The web services in question are fine, and since it doesn't happen all of the time I don't think it's a configuration problem.
Any idea what could be the issue?
turns out the timeout on our load balancer was only 30 seconds. We bumped it up to an hour and we haven't seen the problem again. I'd still like a no session option for BlazeDS.
If you don't know what the operation aborted error is, here's a Microsoft KB Article about it, http://support.microsoft.com/default.aspx/kb/927917 . There's also tonnes of posts about it but the simple answer for it's occurrence is this; the error only occurs if you try to manipulate a DOM element via JavaScript before the element you are trying to manipulate is loaded.
I know how Internet Explorer's (IE) infamous Operation Aborted occurs and know how to fix it. The problem I have is a very weird scenario. Testing locally and on a development machine with IE7, I never ever get the operation aborted error (both sites running as http).
However on our client's testing site it occurs all the time. Unfortunately my testing environment is not the same as the client's testing environment, so that adds some variables to the mix, but the main difference I see is that the client's testing site is using SSL.
Has anyone ever had the Operation Aborted error only for an SSL site?
The other thought that popped in my head was that it was a latency issue. Locally the site loads up almost instantaneously whereas on my client's testing site, the page loads slower. So with that in mind, I got Fiddler running and simulated the performance to run at old school modem speeds, still no operation aborted error locally or on our own testing server.
FYI: The site is an ASP.NET 2.0 Site using ASP.NET AJAX Extensions 1.0. The page with the issue also has the AJAX Control Toolkit's Cascading Drop Down on it.
And yes as far as I can tell all JavaScript that manipulates the DOM is at the end of the markup, not the beginning.
Any help or comments is greatly appreciated.
Well after scouring the Internet I found the issue. It has to do with a bug in the the ASP.NET AJAX client-side framework.
I'll paraphrase what I found:
The issue is a race condition that occurs due to an Internet Explorer/ASP.Net AJAX bug. The probability of encountering this issue increases when the application has a significant number of ASP.Net AJAX enabled server controls on the web page. The issue is explained here, http://seejoelprogram.wordpress.com/2008/10/03/fixing-sysapplicationinitialize-again . I have added this fix to the project I'm working on.
This fix is still required if using ASP.NET 3.5 SP1.
I guess the reason why you don't have SSL on your test box is due to the cost of the certificate. Did you know you can get Free short term certificates? I've often used them to sort out issues like this.
For example RapidSSL do a free 30 day certificate.