connection reset for concurrent usage by two users GAE - google-app-engine

I am trying to access same python web app in GAE from firefox and IE with different user login and when I start the IE session I get the following error with IE going standstill.
why?
error: (10054, 'Connection reset by peer')

I presume this is on the dev_appserver? Bear in mind that the dev_appserver is single-threaded, so it will not handle multiple concurrent users well.
Can you give more detail about exactly what sequence of operations causes this? Are there any stack traces on the dev_appserver console when it happens?

Do you get a similar outcome when you start the IE session first, then the Firefox session? what about trying two IE sessions, two Firefox sessions, that why you can rule in/out browser differences.

Eclipse creates multiple instances on range of ports and few of them conflicts with pythons working. I could not locate the exact port or did not know how to stop eclipse from doing so. I did simple netstat and observed this behavior of port capturing and causing reset

Related

Chrome:POST/OPTIONS requests Fails with net::ERR_TIMED_OUT

The OPTION/POST Request is failing inconsistently with a console Error as err_timed_out. We get the issue inconsistently, it's only observed sometimes. Otherwise the request gets proper response from the back end. When it's timing out, the request doesn't even reach the server.
I have done some research on the stuff and found that due to maximum 6 connections to a resource restrictions it may wait for getting a connection released. But, I don't see any other requests pending ,all the other requests were completed.
In the timeline I can always see that it stalled for 20.00 seconds. Most of the time the time is same. But, it only shows that its been stalled for some time nothing else in the timeline.
The status of the request shows failed ERR_Connection_Timed_Out. Please help.
The Network Timing
Console Error
I've seen this issue when I use an authenticated proxy server and usually a refresh of the page fixes it.
Are you using an authenticated proxy server where you are seeing this behavior? Have you tried on a pc with direct access (i.e. without proxy) to the Internet?
I've got the same problem when I choose another ISP. I thought I would have only to put my new ID and password, but it wasn't the case.
I have an ADSL modem with a dry loop.
All others services were fine (DNS resolution, IP telephony, FTP, etc).
I did a lot of tests (disable firewall, try some others navigator, try under Linux, modem default factory, etc) none of those tests were successful.
To resolve the problem ERR_TIMED_OUT, I had to adjust the MTU and MRU values. I put 1458 rather than 1492, which is the default value.
It works for me. Maybe some ISPs use different values. Good luck.

How to change the admin port using the Google App engine launcher?

It's easy to change the port of the application using the launcher. Go to Edit>>Application Settings (or alternatively Ctrl+i) and change the port. Since I was getting an error similar to the one given below, I changed the application port from 8080 to 48080. Unfortunately, I am not able to change the admin port from 8000 to 48000, because of which I am getting the following error.
google.appengine.tools.devappserver2.wsgi_server.BindError: Unable to bind localhost:8000
I also tried the method illustrated in the following image (my reference being this link):
Regardless of what I try, my web-browsers (Chrome and Firefox) return a message similar to This webpage is not available. Any ideas are appreciated.
I have seen this before, when I had a crashed instance running on the port. You may have a frozen Python script running on that port. On a Mac, I can go to Activity Monitor and kill the process. Not sure if you can do that via task manager in Windows. You may need to restart machine.

Redirect loop when logging in to appengine

(yes - cross-posted from the google-appengine google group...I can't tell if they answer support questions like this there or here or what...it's all kind of a mess :) )
I am having a problem logging in to the appengine console using certain accounts on my google apps domain (but not others).
No matter what browser I use (Firefox, Chrome, Safari, IE), I get a "too many redirects" error on https://appengine.google.com/start when I try to log in using a specific account. I have tried resetting all the browsers as well (clearing all cookies, cache, etc - even trying it on a clean install of an OS) - with no luck. Going directly to https://appengine.google.com/a/domain.name causes the same loop for those accounts. The same thing happens when running the browsers with privacy mode enabled.
One of the accounts having problems is the user nathan.toone on the k9webprotection.com google apps domain - however we can log in with the user "admin" or the user "build-agent" on the same domain just fine (but not "build.agent" or "user2"). It seems to be all over the place as to which accounts are able to log in without the redirect loop and which ones aren't.
I have contacted google apps for your domain support, and they have said that it is outside their scope. They very "helpfully" pointed me to https://developers.google.com/appengine/kb/general - which didn't help AT ALL. :(
Again - the odd thing is that there are some of the accounts on the same domain that are able to log in just fine. Does anyone have any idea what could be happening, or have a way for me to contact someone to get this worked out? I have found a couple of other people saying they have had this problem, but have not been able to encounter a solution.
-Nathan

Unable to access a simple web application (running on Tomcat Server) from another System

I have written a simple web Application which is running(on Tomcat Server) fine on my local system.But when I tried to access from a different system using http:/my_ip_address:8080/Projec1/My_Application. Its showing this error
Network Error (tcp_error)
A communication error occurred: ""
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.
I know many of you must be well versed with this kinda error.But for me its kinda new.I would be happy if you state possible reason and solutions(Please tell me if there is configuration is required in Server step wise)
Thanks All
I forgot tell you all that i found the answer of above question, actually there was proxy setting problem.This is what i did
Open internet option in IE.
Goto LAN setting in Connection option.
In LAN Setting there is advance setting tab, click it.
You will see a Exception box at the bottom.
Type the IP Address form which you want access.
eg. 10.200;*.xyz.com
This setting is to be done on system from where you want to access your web application.
Starting IP address where application is running 10.200.---.--- that is why in exception box it is mentioned as 10.200;*.(your Interanet Server Name)
Hope this will help.
Thanks

What is the cause of intermittent Async_ExceptionOccurred errors in a silverlight app?

I have a Silverlight 3 app deployed at multiple customer sites. Customers are occasionally getting a System.Reflection.TargetInvocationException with an inner exception of Async_ExceptionOccurred.
What is the cause of this? Is it just unreliability in the communications with the server? Is there any way to configure WCF to do an automatic retry of messages?
I've seen it when our IIS servers run out of memory and the the services are no longer responding to the client. They seem to go away with an IIS reset
I'm seeing the same thing with a silverlight app of mine. I can repro this error with Fiddler:
Rules -> Performance -> Simulate modem speeeds
You'll see your WCF svc getting hit, right click it and 'abort session'.
Is it just internet connections flaking out? When this happens in my prod environment I don't see any hit to the WCF SVC when the exception occurs in silverlight. So it's not even getting as far as our server. I have had a VERY similar issue in the past caused by a firewall doing something funny and killing connections.
So I'm left with two options:
update the silverlight app to display a message when we get this error. Maybe alter EVERY WCF hit to attempt 5 times then show an error. Yuck!
isolate any possible firewall issues. Run a test harness to repro the error. Test it in environments with/without any firewall.

Resources