At my job, we use the debugging tool Charles Proxy a lot. So I always have it running in the background. Sometimes it's recording, other times it's not.
However, lately it has started acting up. For every web request I do, there is a 1-3% chance that it will fail to connect with the reason: "Connect: Connection timed out: connect"
Test case
I did a test with Charles: Use the 'repeat advanced' option on a file to fetch it 50 times:
As you can see, 2 of them failed. (And it took it 21 seconds to timeout). The 98 other times, it took ~4ms to complete the request.
I did the same test with Charles closed and Fiddler opened instead.
After 400 requests of the file, not a single one had failed.
Happens on normal usage
Here, it happened when I opened the company game site. A rather important request failed and thus, the site never fully loaded.
I have tried
I tried restarting my computer.
I tried updating to the newest version of Charles.
I tried uninstalling and installing Charles.
I tried disconnecting from the VPN we're on.
I tried closing down Charles and that seems to fix it. But I need to have Charles running and I don't want to open and close it all the time.
I tried using Firefox instead of Chrome and it seemed to happen very rarely or almost never. However Firefox is really bad to use when working with Flash.
Edit (Chrome net-internals)
I logged the output from chrome://net-internals/#events when trying to load a file that failed.
Pastebin dumps: http://pastebin.com/dgMaLMKc then http://pastebin.com/dAGpJCJy
It would seem this was caused by the program Ad Muncher. After closing it down, the timed out connections has apparently stopped.
Related
I am getting this weird prompt window from yesterday since restarting my laptop on every redirection of url or whenever I open the new tab it just pops up. Going to localhost:8080 show unauthorized. Secondly in my developers option I have started seeing following 2 errors
1 content.static.js:20 GET http://localhost:8080/contentDocumentStart.js 401 (Unauthorized)
2 GET https://dw4sx0xk0hu8c.cloudfront.net/contentDocumentStart.js 403
Kindly if anyone can help. I have searched, came across few of the tomcat solution but I don't know what is the issue or how to sign in (more importantly whats it requiring it for).
For some odd reason I tried updating chrome and restarting it several times but in vain. The thing that worked is I restarted my PC (for some new software changes to take effect). And while browsing I noticed I wasn't getting the pop up window any more on chrome. So if it happens with someone, try restarting the PC.
Normal js code (no service worker, but the app has a manifest with an empty service worker).
A simple timeout to an ajax call that's the code.
I close all chrome tabs, I close the process in task manager, no more chrome processes and yet I still get requests on my server. This happens locally and on the server, I know this because I can see the cookies sent and for which user id is needed.
Also I know that chrome is running the code because there is a date in the request and is updated as it go.
Triple checked that chrome is closed on all users and all processed in task manager.
Is not a coincidence because at this moment I have 2 different users (different chrome profiles) doing this. Also in my dev server there are a lot of users with the same behaviour.
I'm also not sure is chrome, but has to be, node.js alone can't change the time of the request.
Win 10 and Chrome Version 60.0.3112.90 (Official Build) (64-bit)
Terrible and I don't know what to do...
if I restart my node.js server all the requests stops.
Was my mistake! As I have server side rendering (with react) I forgot that the timeout was also run on the server side. The fix was to don't run any timeouts on the server side.
Thanks anyway for the answers. I was concerned how chrome was still running my js code even shut down, made no sense at all!
i have made a flash chat application on Flash Builder 4.6 which connects to Flash Media (Development) Server on my centos5 32bit server, the problem is when i leave it open in browser about 2 minutes idle, then trying to call the netconnection to get the chat history or to send a public message or to invoke a function at the serverside with the nc.call() method, it suddenly says netconnection.connect.closed.. UNLESS i call, it doesnt gives me a connenction.closed event..
while this happening, i am looking at the fms admin console for active users, but the client doesnt drop and seems still connected to server..even i close the browser, client is still there in the fms console.. (normally, when i close the browser or when i use the nc.close() the client disconnects and i see the quick change in the fms admin console..
then still watching the fms admin console, after about 10 minutes the client drops..(it is normal i think)
i tried the same app with the connection to localhost, it works very well, i left the app open for a very long time idle, and then tried the nc.call() it worked fine.. but when i try the app on the my server, i had the problem.. i tried both fms 3.5 and 4.0.3 on my server but i had the problem too.. but on localhost it works so i think the problem is not about versions it is about something different with the connection to the server..
also the pepper flash player is disabled..and the problem is not about the autocloseidleclients property in the server.xml, application.xml vhost.xml config files. the problem is something different with the connection may be about firewall, tcp, router etc.. i dont know but i really need help..
thanks for reading..
Hm, if NetConnection works using sockets, then as far as I know, on Windows, the only way you can determine if a socket is closed is to try and write something to it; if it fails, then it's been closed - hence call() actually closing the connection after it's been idle for too long.
When you close the browser or call nc.close(), it's a specific request - normally on the server you'd also implement something like "if I haven't received anything in X seconds, disconnect the socket", which would trigger a callback on the client end.
I'd implement a sort of keep-alive; every 15/30 seconds, send a simple ping to the server, which will keep your connection open.
From last 1 week i am facing strange issue in google hangout. as i join a meeting first a message pops up
Your microphone is not working or is hardware-muted!
then after few seconds i see message
Couldn't start the video call because of a network error.
Please check your firewall settings and try again.
with button to try again. and it keeps going on in this way.
I have checked firewall settings
I have tried with different networks
I have tried with different computers
I have tested microphone and speakers they are correct
I inspected ajax calls in firebug and i see this
NetworkError: 404 Not Found - https://plus.google.com/u/0/talkgadget/_/ping?id=1
NetworkError: 404 Not Found - https://plus.google.com/u/0/talkgadget/_/ping?id=2
POST https://plus.google.com/hangouts/_/channel/bind?...200F2A8A372&RID=67018&AID=84&zx=2a53yvv7e45w&t=1 Aborted
At google Community somebody answered like this:
I have found the culprit. I use Spybot Search & Destroy's Anti-Beacon software to block telemetry data that Windows 10 constantly sends to Microsoft. This is why trying multiple Windows 10 machines that I have configured did not alleviate the problem. Somehow one of the IP block entries it adds to the Windows Firewall now conflicts with Google Hangouts. I will report this to the software vendor.
Source: https://support.google.com/hangouts/forum/AAAAfpFnBZ8mdNNg8LNvNg/
When I was validation my Windows Store App I got the following error:
Application Error: Application Launch was not detected for application
App. This could be because your application failed to launch
correctly. Please consider re-running the test and avoid interacting
with the application while tests are running.
What does this mean? The app will not validate.
I thought it was a bit weird and I couldn't find anything when I googled it but people who had almost the same problem as me, though rather than launching it was failing to sleep. This was just plain odd.
I tried to launch the app from Visual Studio 2012 just to prove to myself that it did start properly and for some crazy reason it didn't work. I usually test the game on my Local Machine rather than the Simulator but now, for some reason, it was set to the Simulator and I have been having problems getting it to start lately (the simulator).
I changed it back to the local machine and ran the tests again. This time it worked.
So, if you get this error it might be time to see if your simulator works and if not, have the Local Machine set as default to run with.