On 10.05.2012 11:24, Agnieszka Allstar wrote:
Obviously this has sth to do with the fact that in A case the mod_jk.log says the request is recoverable, whereas in B case it's unrecoverable but I can't really tell what's the cause after looking at mod_jk src.
Just in case you are still following the list: in general a request is recoverable, if mod_jk wasn't able to send a request packet to Tomcat. If it has already sent the request there and the communication fails later, failing over to another Tomcat would possibly mean the same request were handled twice. Not the right decision in general, e.g. if the request triggers a shop order.
The workers.properties attribute reciovery_options influences this in detail, e.g. you can decide that GET and HEAD requests should always be recoverable, even if they had already been sent.
For your two examples it would indicate, that they failed at different points of the communication, e.g. in one case mod_jk could not connect to Tomcat (recoverable), in the other case Tomcat already received the request but did not response (in general unrecoverable).
Regards, Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
