https://issues.apache.org/bugzilla/show_bug.cgi?id=44571
Summary: Limits busy per worker to a threshold
Product: Tomcat 6
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Connectors
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
On a high load tomcat server, If a lot of requests is received suddenly, it
will take a lot of time to serve the requests, but apache still send more
requests to the tomcat, then tomcat become slower and slower. Since the server
takes no response, some web clients may send the request again, make tomcat
server more slower. It is something like congestion.
I write a patch to limit busy per worker to a threshold. Define the threshold
in worker.properties. If all workers reach the threshold, further request will
get a 503 response. And sticky session parameter is ignored if the worker
reaches the threshold.
It is very simple to configure, just add the busylimit to the worker. default
is 0, which means no limit. eg.
worker.test-1.port = 8009
worker.test-1.host = localhost
worker.test-1.type = ajp13
worker.test-1.busylimit = 10
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
