hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7688) When a servlet filter throws an exception in init(..), the Jetty server failed silently.
Date Wed, 02 Nov 2011 17:53:32 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-7688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142351#comment-13142351
] 

Uma Maheswara Rao G commented on HADOOP-7688:
---------------------------------------------

Hi Nicholas,
 Yes, that is correct with Servelet inits. Also we have the control parameter for load on
start ups. But i dont see anywhere in the spec related to Fileters, they will have the same
rule as servelet inits. 

As per my debug information, always filter init is getting invoked when it is loading the
contexts. Since we are throwing the exception from init, context loading is failing. So,the
application is not deployed propely. Whenever first request comes it is giving 503 service
unavailable response.

Am i missing something here? 
                
> When a servlet filter throws an exception in init(..), the Jetty server failed silently.

> -----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7688
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7688
>             Project: Hadoop Common
>          Issue Type: Improvement
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Uma Maheswara Rao G
>         Attachments: filter-init-exception-test.patch, org.apache.hadoop.http.TestServletFilter-output.txt
>
>
> When a servlet filter throws a ServletException in init(..), the exception is logged
by Jetty but not re-throws to the caller.  As a result, the Jetty server failed silently.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message