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

Steve Loughran commented on HADOOP-7688:
----------------------------------------

It's part of the Servlet API spec that a servlet may not get its init() call 
until the first HTTP request comes in. This stack trace implies that the same 
thing happens on filters. 

Looking at the Servlet 3.0 spec, all they say is "After deployment of the Web 
application, and before a request causes the container
to access a Web resource, the container must locate the list of filters that 
must be
applied to the Web resource as described below".

This could imply that it's done when a request comes in. There's a valid reason 
for doing that -it allows people to set up filters after a servlet context is 
brought up, which is something I've done in the past. 

Are all the filters Hadoop-specific? If so they could have a base class that 
logs the exceptions, reports them. Then have a preheater that GETs all the 
servlet pages; that's always handy for compile-on-demand JSP pages anyway; if 
any page fails the preheater can report it. 
                
> 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
>            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

        

Reply via email to