top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Usage of maxActiveConnections in Apche

0 votes
288 views

I was looking at using the maxActiveConnections in the application context, what I find is. When I reach the limit, as expected the server will not create a new session, however does return a http 200 status code.

I am wondering would it be possible for me to change this behavior to return say a 300 range code to redirect to (in a production environment) load balancer.

I can see some potential issues with this, like the possibility of an infinite loop, but for now I am just exploring possible ways to prevent my tomcat servers becoming overloaded.

Does anyone have any thoughts or ideas for this type of solution?

posted Aug 13, 2013 by Kumar Mitrasen

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

Try "maxConnections" on the HTTP connector.
https://tomcat.apache.org/tomcat-7.0-doc/config/http.html
or the AJP connector, depending on how your proxy is connecting to Tomcat.
https://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html
"The maximum number of connections that the server will accept and process at any given time. When this number has been reached, the server will not accept any more connections until the number of connections falls below this value."

answer Aug 13, 2013 by Seema Siddique
Similar Questions
+2 votes

I am asking best practice/info/docs of how to have 2 apache web servers in load balancing.
- Which httpd module do I have to load in the http conf?
- I was reading that I have to have a web load balancer on top of them? Is it necessary? Can they accept requests from a cisco /F5 load balancer?
- What about persistent connection?
- Also we''ll have a mySQL server? Any more info about this?

+1 vote

I have an idea how to setup Apache for doing load balancer based on mod_proxy and mod_balance modules. But in my case the backend server requires ssl client certificate authentication and therefore the Apache Server cannot terminate the ssl connection.

I do no need http session cookie stickyness. The application is stateless. Can I somehow configure Apache as a transparent balancer?

Or I should use even another software - squid, iptables? The backend application is a web service running on Tomcat.

+1 vote

I would like to know, if there exists any solution in order to synchronize (replicate) sessions between two httpd servers which are configured as load balancers using mod_proxy_balancer? Considering HAProxy, the same functionality exists; it is possible to synchronize the stick table between HAProxy instances. Does mod_proxy_balancer use stick table? Is it possible to synchronize the stick table between two mod_proxy_balancer instances?

...