>
> We have an application running as a webapp which requires legacy
> systems and network resources which are not fault-tolerant. Luckily
> these resources are stateless. So we have replicated these
> resources so
> that one is available per tomcat instance. When we attempt
> to use one
>
you find this useful?
Byron
-Original Message-
From: Dan Thiffault [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 15, 2005 1:41 PM
To: Tomcat Users List
Subject: Re: Failing a JK Worker thread
I didn't hear back from any one so I looked through the code. I couldn't
find any sign of code
What is the situation where you find this useful?
Byron
-Original Message-
From: Dan Thiffault [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 15, 2005 1:41 PM
To: Tomcat Users List
Subject: Re: Failing a JK Worker thread
I didn't hear back from any one so I looked through the
Dan Thiffault wrote:
if (d->status=500) {
jk_log(l, JK_LOG_ERROR,
"Tomcat server returned status=%d",d->status);
JK_TRACE_EXIT(l);
return JK_FALSE;
}
I may end up using a case statement and preventing apache from trying
the next worker on bad request or something like that. Ho
I didn't hear back from any one so I looked through the code. I
couldn't find any sign of code that would provide this functionality,
so I added the following before line 605 of jk_ajp_common.c. I
recompiled and it seems to be working as intended so far.
if (d->status=500) {
jk_log(l,
I am running apache web server 2.0.49 connected to tomcat 5.0.28 using the jk
connector version 1.2.8. From my understanding, if I set the reply_timeout
property of an ajpv13 worker, once the reply_timeout elapses for a particular
request to a worker, apache web server will make a new request
