By default, Apache2 seems to allow only 1 connection per IP address.
How do I configure Apache2 to allow multiple simultaneous connections from the same IP address?
Here is my situation:
- a web app being hosted on a server.
- a remote client makes an request that may take 15 seconds to complete.
- the same remote client makes another (independent) request.
- at present, the 2nd request sits in a queue until the 1st request completes, since Apache2 seems to impose a limit of 1 connection per IP address.
How do I override this default behaviour and allow the 2nd request to be processed in parallel?
thanks in advance, David Jones
This topic is a bit outdated but i hope that my post may be useful for someone who is experiencing similar problem.
I have noticed that such a behavior is PHP related if you are using built-in sessions functions and session data is kept in files. PHP acquires an exclusive lock of the session file and if another process is trying to start session it waits until lock of this file will be released. So the simpliest solution is to call session_write_close function (which releases lock) as soon as session data is not needed anymore
That doesn't sound right. Apache doesn't limit it to one connection per IP. It sounds like whatever you're requesting from the server is causing the holdup. Apache is likely passing both (or more) connections to your app, and the app is causing the bottleneck.
Can you elaborate on your setup a bit further? What is your app written in? If you throw up a static HTML page, do you get the same result?