Nope. The spec doesn't spell this out. If your feeling daring, you could
write a filter that tries to set and reset the Thread.priorities on the fly.
Then if your JVM pays attention to the thread priorities - you might get the
tweaking you need. (You can also do this in a Valve if you want to be lower
in the stack but I really doubt any of this is useful but its a great time
waster on a cold rainy day)
For example - without all the need try catches ...
doFilter(...) {
int newPriority = magicMethodToDeterminePriority(request);
int oldPriority = currentThread().getPriority();
currentThread().setPriority(newPriority);
chain.doFilter();
currentThread().setPriority(oldPriority );
}
-Tim
Rui Zhang wrote:
Hi all,
Is there any infrastruture availabe (or at least any possiblities) in
Tomcat to tune the QoS requests are receiving?
For instance, is it possible to give differentiated treatments to
requests of various importance, by granting them different amount of
resources, queueing them differently, etc?
I realise my questions might be a bit vague, as I don't have too much
insight about Tomcat. All I'm looking for are some knobs in Tomcat that we
can turn to affect its performance, either observed by different groups of
requests or by all the requests on a whole. If there are no such knobs at
all, would it be possible to amend the current Tomcat with it?
Any advices (or at least what readings I should do to acquire that
knowledge) would be greatly appreciated.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
