Hello Mladen ,
yes Remy, we have currently no chance inside tomcat. :-(
My szenario is really important when automatic alive monitoring
detect that inside an application or node is something wrong (Out Of Memory Exception,
all thread hang, detect a deadlock or other nice application relevant bugs/feature)
What I want is, that we can stop request sending from mod_jk side at a single node. Why we can't stop all requests for a worker, when we set a flag worker.node1.active=false ? Ok, then no application on this node get request, but we can control the tomcat restart.
Peter
Remy Maucherat schrieb:
Mladen Turk wrote:
I think that this is the Tomcat responsibility. If inside redeployment, it should hold the request until finished. For mod_jk you can set the socket_timeout that will cause the failover to another worker (if redeployment takes more then 60 seconds).
There is no way to hold a particular request.
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
