Thank you very much. I had also found those parameters, which limit the connection between the client and Apache. But they do not stop the execution within JBoss I assume.
In fact, is there any way JBoss can stop execution of a timed-out request? What if I program an infinite loop in a servlet? Does that mean that JBoss loses one thread to a useless infinite execution every time some one calls that servlet? Apache gives them a time-out, but the JBoss thread continues I suppose.
Is there a way to make JBoss stop execution of requests that have timed out?
Thanks in advance for any help.
I'm now searching for the same functionality that bunkenburg described. Is there a way to set a request time in Tomcat? It would essentially be what maxIdleTime does for Jetty. 
I'm looking for a global time out that will kill a Tomcat request thread if it has not responded by a certain timeout. I see the mod_jk settings mentioned above, but I have the same issue with them, which is that JBoss/Tomcat will still be trying to process the request, long after the client is gone.
Does something like this even exist in Tomcat?
I see connectionTimeout in server.xml but I realize that's not what I'm after.
PIER Sytems, Inc.
 - http://docs.codehaus.org/display/JETTY/Configuring+Connectors