You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Brian Maher <ma...@brimworks.com> on 2003/10/25 14:48:12 UTC
mod_jk timeout?
I noticed this message from Glenn Nielsen recently on this mailing list:
http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg47341.html
It appears that hgomez submitted a bunch of code that allows you to
configure a ping/pong mechanism that helps it detect hung tomcats. I'm
very much interested in this code, but wonder if it could also detect
an aborted apache process?
Here is a simple test I performed recently with my server configured
like this: (Apache (1.3.x) <---(mod_jk)--> Tomcat 4.1). On all my
apache requests, I set a hard_timeout() using mod_perl. It is pretty
easy to see that this hard_timeout works fine by looking at apache's
/server-status page. My next test was to see if this hard_timeout()
worked for Tomcat. So, I wrote a simple JSP page as such:
<%
while(1) {
Thread.sleep(100000);
System.out.println("hi\n");
}
%>
When I request this page and tail my log file, I see "hi" printed over
and over as I would expect to see. However, the disturbing part is
that even after the hard_timeout() has expired, this thread is still
executing (since I see a bunch of "hi\n" in my log file). I check
apache's /server-status page and the process that was servicing the
request is long gone.
Could this recently submitted ping/pong code also be used from the java
side to detect when the Apache side is no longer servicing the request?
I'd be willing to help make this happen if someone could give me some
guidance.
Thanks,
-Brian
P.S. Please note that I am not on the tomcat-dev@ list.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: mod_jk timeout?
Posted by ma...@coremedia.com.
On Mon, 27 Oct 2003, Henri Gomez wrote:
> If the thread on java side is a long running task or a blocking task,
> it should be handled by the servlet engine and sus some watchdog support
> should be added in Tomcat.
>
> In you're exemple I didn't know how the thread could be ever finished !!!
In theory, that's what Thread#interrupt is for. It asks the thread to shut
down, resulting in setting the #interrupted flag / an InterruptedException
on potentially blocking calls such as wait() or sleep(). One could
interrupt named jsp like that.
However, dealing correctly with InterruptedExceptions is hard (you should
leave your objects in a meaningful state) and since InterruptedException
also is a checked exception, many people choose to
catch(InterruptedException ie) {}, even(?) Sun ORB code does so (not to
speak of my own).
Those threads are inevitably lost.
Matthias
--
Matthias Ernst
Software Engineer
CoreMedia - Smart Content Technology
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
Re: mod_jk timeout?
Posted by Henri Gomez <hg...@apache.org>.
Brian Maher a écrit :
> I noticed this message from Glenn Nielsen recently on this mailing list:
>
> http://www.mail-archive.com/tomcat-dev@jakarta.apache.org/msg47341.html
>
> It appears that hgomez submitted a bunch of code that allows you to
> configure a ping/pong mechanism that helps it detect hung tomcats. I'm
> very much interested in this code, but wonder if it could also detect an
> aborted apache process?
>
> Here is a simple test I performed recently with my server configured
> like this: (Apache (1.3.x) <---(mod_jk)--> Tomcat 4.1). On all my
> apache requests, I set a hard_timeout() using mod_perl. It is pretty
> easy to see that this hard_timeout works fine by looking at apache's
> /server-status page. My next test was to see if this hard_timeout()
> worked for Tomcat. So, I wrote a simple JSP page as such:
>
> <%
> while(1) {
> Thread.sleep(100000);
> System.out.println("hi\n");
> }
> %>
>
> When I request this page and tail my log file, I see "hi" printed over
> and over as I would expect to see. However, the disturbing part is that
> even after the hard_timeout() has expired, this thread is still
> executing (since I see a bunch of "hi\n" in my log file). I check
> apache's /server-status page and the process that was servicing the
> request is long gone.
>
> Could this recently submitted ping/pong code also be used from the java
> side to detect when the Apache side is no longer servicing the request?
>
> I'd be willing to help make this happen if someone could give me some
> guidance.
The timeout support help the native side detect a problem on the java
side, for exemple a HUNG tomcat.
If the thread on java side is a long running task or a blocking task,
it should be handled by the servlet engine and sus some watchdog support
should be added in Tomcat.
In you're exemple I didn't know how the thread could be ever finished !!!
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org