Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is mod_authnz_external thread-safe? #20

Open
GoogleCodeExporter opened this issue Mar 24, 2015 · 0 comments
Open

Is mod_authnz_external thread-safe? #20

GoogleCodeExporter opened this issue Mar 24, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

This is how I set up a "stress test" for Apache:

1. Set up a web page that issues 100 AJAX requests within a short period of time
2. Using the about:config page in Firefox, modify the parameter 
network.http.max-persistent-connections-per-server to allow 50 simultaneous 
connections 
3. Set up Apache so that the MPM operates in worker mode (rather than prefork).

What is the expected output? What do you see instead?

When I run the stress test, about 10% of the AJAX requests are lost, and the
Apache error logs contain entries like this:

[cgid:error] [pid 27442:tid 1] AH01239: cgid daemon process died, restarting

There are several ways I can make the problem go away: (1) change the MPM
to use prefork rather than worker, (2) change the authentication mode to use
file authentication instead of external authentication, (3) decrease the 
number of simultaneous connections used by Firefox.  However it appears that
mod_authnz_external is unable work properly under heavy loads when threading
is used.

What version of the product are you using? On what operating system?

I am running Apache 2.4.10 with version 3.2.3 of mod_authnz_external

Please provide any additional information below.

I did my testing on an HP Integrity box running HP-UX 11.31.  

If mod_authnz_external simply does not support thread safety, then I will set 
up my Apache server to use prefork, but I would like to use threading if
possible.


Original issue reported on code.google.com by [email protected] on 4 Feb 2015 at 8:06

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant