tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty" <mgai...@hotmail.com>
Subject Re: Possible to send 503 status over JK?
Date Tue, 25 Jul 2006 20:32:27 GMT
The only viable solution is to setup a filter and monitor invocations of init(), doFilter and
destroy() method where the timeout could be calc'ed as

getCurrentTime() - lastgetCurrentTime() > ElapsedTimeParameterFromFilterConfig.getInitParameter("Timeout")
check out 
http://tomcat.apache.org/tomcat-5.0-doc/servletapi/javax/servlet/Filter.html
for details..

Anyone else ???
M-
*********************************************************************
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



----- Original Message ----- 
From: "Rick G" <tomcatdev@vidyah.com>
To: "'Tomcat Users List'" <users@tomcat.apache.org>
Sent: Tuesday, July 25, 2006 1:54 PM
Subject: RE: Possible to send 503 status over JK?


> Martin,
> As for proxy servers, no I have not looked into that. But I don't think I
> would want to add another layer to the mix just to have to parse all
> requests for the off chance that the webapp is stopped.  Especially when
> Tomcat knows that the webapp is unavailable, there should be a simple option
> to set if Tomcat generates its own status pages or returns the proper http
> status code so that said errors can be handled by apache instead.  It does
> already properly return on a 500 application error.  Tomcat gives you its on
> 503 error page if the webapp is down, so it shouldn't be that big of a
> stretch to have it just return a 503 status code so that apache can catch
> it.  Again, I may be missing something, but I'm reading through the code now
> to see if I can get it to return the 503 status code when applicable.  It
> seems to me like this would be the correct behavior, at least when using a
> front end web server.
> 
> -Rick 
> 
> -----Original Message-----
> From: Martin Gainty [mailto:mgainty@hotmail.com] Posted At: Tuesday, July
> 25, 2006 10:30 AM Posted To: Tomcat Dev
> Conversation: Possible to send 503 status over JK?
> Subject: Re: Possible to send 503 status over JK?
> 
> 
> Rick-
> 
> Have you looked at proxy servers?
> http://www.experts-exchange.com/Networking/Q_21679699.html
> 
> M-
> *********************************************************************
> This email message and any files transmitted with it contain confidential
> information intended only for the person(s) to whom this email message is
> addressed.  If you have received this email message in error, please notify
> the sender immediately by telephone or email and destroy the original
> message without making a copy.  Thank you.
> 
> 
> 
> ----- Original Message -----
> From: "Rick G" <tomcatdev@vidyah.com>
> To: "'Tomcat Users List'" <users@tomcat.apache.org>; "'Martin Gainty'"
> <mgainty@hotmail.com>
> Sent: Tuesday, July 25, 2006 12:37 PM
> Subject: RE: Possible to send 503 status over JK?
> 
> 
>> Hi Martin, doesn't the example you listed involve the webapp actually
>> running to return a 503 in a particular circumstance?  I'm trying to
> handle
>> a 503 when the webapp is actually stopped, by the manager app/JMX.  So
>> nothing code/config wise in the webapp would fix the problem that I can
>> think of, it would have to be a code/config change for tomcat itself.
> This
>> is why I was looking for the default request handling pipeline order.
>> 
>> In my initial browsing of the code...
>> org.apache.ajp.RequstHandler::decodeRequest(Ajp13 ch, Ajp13Packet msg,
>> BaseRequest req) int
>> The comments for the return value say...
>> "@return 200 in case of a successful decoduing, 500 in case of error."
>> But I'm still reading
>> 
>> Again if anyone has any info that can point me in the right direction, I
>> would appreciate it.
>> 
>> -Rick
>> 
>> 
>> 
>> 
>> -----Original Message-----
>> From: Martin Gainty [mailto:mgainty@hotmail.com] 
>> Posted At: Tuesday, July 25, 2006 9:01 AM
>> Posted To: Tomcat Dev
>> Conversation: Possible to send 503 status over JK?
>> Subject: Re: Possible to send 503 status over JK?
>> 
>> 
>> If you dont mind handling this programmatically..check out this Filter for
>> 503 errors http://java.sun.com/developer/JDCTechTips/2001/tt0626.html
>> M-
>> *********************************************************************
>> This email message and any files transmitted with it contain confidential
>> information intended only for the person(s) to whom this email message is
>> addressed.  If you have received this email message in error, please
> notify
>> the sender immediately by telephone or email and destroy the original
>> message without making a copy.  Thank you.
>> 
>> 
>> 
>> ----- Original Message -----
>> From: "Rick G" <tomcatdev@vidyah.com>
>> To: "'Tomcat Users List'" <users@tomcat.apache.org>
>> Sent: Tuesday, July 25, 2006 11:21 AM
>> Subject: Possible to send 503 status over JK?
>> 
>> 
>>> Hi All,
>>>  I saw a similar question asked a while back about using a custom 503
>>> errorpage, but never saw an answer.  I'm looking to, if a page is
>> requested
>>> for a webapp that has been stopped, instead of returning the canned
> Tomcat
>>> 503 Error page, to have it return a 503 status code instead so that you
>> can
>>> have Apache handle it and show a custom (pretty) error page.  
>>> 
>>>  It seems like on a 503, Tomcat generates its own 503 page and returns
>>> status 200 so Apache doesn't know it needs to do something.  Some one
>> please
>>> correct me if I'm wrong and/or there is an easy solution to this.
>>> Otherwise, anyone familiar or have a link with the standard processing
>>> pipeline in tomcat 5.5.x and know the order of valve/filter execution
> that
>>> can point me in the right direction?
>>> 
>>> Thanks for any help,
>>> Rick G
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To start a new topic, e-mail: users@tomcat.apache.org
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>> 
>>>
>> 
>>
> 
> 
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
> 
>
Mime
View raw message