I'm working with a Classic ASP web app that typically runs well considering the old technology. It is an online support chat application that basically refreshes the client side Live Monitor page every 10 seconds to see if there are any pending chat requests. The past few days, a lot of our users are having a problem where this page either just ends up refreshing and going blank white (with no html in view source), or it goes to a generic IE error page "This program cannot display the webpage" - the same error you see when you are offline. I was able to recreate the issue after hours when I was the only user in the chat system, so it's not a matter of an overloaded server I don't think.
I've tried the following to no avail:
Recycle Application Pool
Reboot IIS Server
Change refresh from javascript to meta tag
Check IIS Error logs (nothing)
Check IIS event logs (nothing)
One thing that seemed to work for me, but didn't work for everyone else, was to disable our network Proxy server settings in the browser. Once I disable this, I can't get it to error out anymore... however, other users aren't quite so lucky.
Any thoughts on where to go with this? I'm at a bit of a loss here...
Thanks,
Shawn
We are finding the same problems in a .Net solution. It looks as if the issues are related to SQL Locking so we're working on those as we find them.
Related
I'm having issues with my Socket.IO project.
It's a complex back-office built with create-react-app. There is a lot of different web sockets handlers all over the project. It's nicely architectured, so there is a low amount of messy code. Nevertheless, on one of my pages (the main one), the server is sending every 5s some live metrics through web sockets to any of the clients connected to that main page.
If I take a look at my client app, everything works fine:
The update live metrics happens every 5s as expected
If I stay on that page, reload the page. Then the messages keeps coming every 5s:
As seen in the WS Network panel pf the Chromium devtools
But the Javascript eventListeners are not triggered. I've tested to see if they were setted properly after the refresh and it's true. I'm not sure where to look more to debug this.
I thought that if the network is recevings the web socket messages and that the listeners are setted up, there is no reason that the callback function is not called.
Thanks in advance,
Please note that this question is in consequence of another question: "Codename One - ToastBar when “No connectivity detected"
What is a correct approach (in Javascript or JQuery) to deal with Internet connection unavailability (that is common on mobile devices)?
Every time that there is a networking error, I would like to show a message to the user (like this one: https://i.stack.imgur.com/Ll6jD.png) and pause the Internet activity of the web page, in a way that no errors are generated (and the messages written by the user, for example in an html form, are not lost). The Internet activity should be (automatically) restored when the connection will be available again.
This should be a convenient way to allow people to interact with a web site (from mobile devices) without the risk of losing their posts or comments and without receive errors when they click a link.
This functionality should be as much as possible independent from the specific web site. What is a correct way to implement it?
use jquery plugin like this :
Offline.js
I am not really sure how to fully explain this problem. There has been this ongoing issue where SOME clients web browsers are not able to get the latest JS file for my website no matter what they do. Mind you, everything works fine when I visit the webpage from my workstation, but for others the js files are old versions.
Things we have tried:
-Appending a random parameter to the end of the js file <script type="text/javascript" src="~/scripts/Main/main.js?319"> </script>
-Force-refreshing the cache (Ctrl-F5)
-Setting Internet Options browsing history to "Everytime I visit a webpage"
-Clearing all browser data (IE, Chrome, Edge)
What is getting me is this doesn't happen to everyone, and it doesn't happen all the time. Only occasionally and only to some users and the issue always eventually resolves itself within a day or two. Whats going on here?
Website is an ASP.NET MVC application running on IIS8 on Windows Server 2012 R2
I don't have a silver bullet for you on this but my application has the same issue. In my instance we have a third-party authentication system (specifically, Tivoli Access Manager) between our clients and our server. Our suspicion has always been that something in TAM is caching stuff invisibly to us, and despite of any settings we have in IIS or what have you.
In your environment do you have any proxies or middle tiers that could be performing caching on your app's behalf?
How can we detect through PHP or maybe in node.js or other languages if a web page crashed (without the browser EXITing) so that when a user press the "reload" button on the "Aw Snap" page in chrome certain specific content inside the page can be shown in this particular case (crash case).
In a crash without EXIT, a browser shows per example in Google Chrome the famous "Aw, Snap!" page.
I don't want to know how to capture if the user refreshed the page or the page reloaded which can be known quite easily with different methods [one example see this PHP this code which can detect if users refreshed the page on major desktop/mobile browsers except IE unfortunately this code does not capture a crash event and the fact that user might request again the same page after a crash.
I tried using "register_shutdown_function", and some other maneuvers using connection PHP functions like "connection_aborted" etc... but with no success. I figure out a sloppy way through the use of session variables but probably there are better clever manoeuvres.
Any help or suggestion would be greatly appreciated. Any solution in nodejs will be also welcomed.
web brower crash because too many process from your browser to PC of Client.
this crash can't detected by php because PHP server scripting. and you have question.., why not use JS for detect crash of browser?, because JS created just for controller website,. if you force to checked that use ajax, node, etc you can't do that, why? because the problem comes suddenly
and detected crash browser from php is impossible.
Situation:
I have a website that is written in Java (1500 LOC) and compiled to javascript with GWT (Google Web Tools). I started observing "Warning: Unresponsive script" on my website few weeks ago. I got this pop up warning 22 times out of 25 tries.
I can fix this by clearing Firefox browser cache. And after that I saw warning message 1 time / 25 tries.
I am trying to figure out what's the root cause of this. It seems to be a client side issue. My customers are probably not seeing this since they don't load that website as often as I do. However, I feel like they might run into this issue in this future. I wonder if there are something I can do on the server side to eliminate/reduce the occurrence of unresponsive script warning.
Questions:
I compared Firefox "about:cache" before and after I load my website. The only difference is that a 43 byte cache gets created in memory every time I load the website. Is this something normal?
I thought cache is to help users load websites faster, what could be happening in my case? (I guess my website generates new cache every time on load and old cache are not used?)
Since clearing the cache can fix this issue, how can I automatically clear cache when user closes my website?
Could there be an issue in GWT compiled javascript? Could network speed also be a factor?
What else do I need to check and what are the potential solutions to resolve this issue?
Install FireBug to Firefox and see what scripts are timing out. Given this is GWT, there is a good chance something is getting stuck on the server side. If so:
Run you server under a profiler and see where are the host spots or bottlenecks. I prefer JProfiler, been using it for 10+ years.