AFAIK this configuration will not exist.
Also is is doubtful whether this is a useful configuration. Because you will throttle the overall throughput.
Why you want such kind of behaviour?
because we want to ensure that the important request occupied more threads.
assign 150 thread for http://www.abc.com/aa/xx.jsp
if other 50 threads are running ,all assigned threads are not occupied, a new request coming . this request must wait . while non-assigned threads have a free thead, handle this request.
AFAIK, configuration files can not solve this problem.
perhaps, i will develop some mbean servers, or rewrite some interface implementation.
does it make sense in a web app to prioritize requests considering urls?
You could implement such functionality in a Tomcat Valve. Just make sure you really get the thread handling correct
A good idea would be to also add a MBean so you can look into the Valve and perhaps reset/change the settings in runtime easily.
....a Valve could at least quickly throw a 500 for unwanted connection...
thanks, i plan to implement the valve .and i try to add a mbean .