Geek asks and answers

Getting the "maximum number of connections reached" error with a large amount of HTTP requests in the Google engine

I am trying to stress-test my GAE application to see how it works with a large number of concurrent users. I tried to have 100 threads, each of which sent https requests in 1 second, but half of them failed with the status code 503: message: "Error: connection not allowed: maximum number of connections reached."

This is a paid application, so I tried updating the instance class and setting up some idle instances, but there seems to be a difference.

Is there a limit on the number of simultaneous connections? Or is it because all requests are generated from the same host?

thank

EDIT: Reply to Kyle: I use jmeter and send 100 simultaneous requests to google.com, it has no problems. Answer to Nick: I do not expect individual clients to send many simultaneous requests, I tried to simulate 100 users sending 1 request each.

+5
source share
1 answer

Unbeknownst, a colleague added a custom damping filter to our application :) I removed this from web.xml and solved the problem.

+1
source

More articles:


All Articles