[jetty-discuss] [jira] Commented: (JETTY-164) Regularize handling of errors on deployment such that the whole server does not necessarily fail

[Greg B. (JIRA) <ji...@co...>]

    [ http://jira.codehaus.org/browse/JETTY-164?page=comments#action_82654 ] 
            
Greg Brail commented on JETTY-164:
----------------------------------

I've noticed this as well.

In particular, if a web app contains servlets that have "load-on-startup" set, and the "init" method throws an exception (including UnavailableException), then the whole web app is marked as "failed". This is new behavior since Jetty 6.0. It looks like it's caused by a new "catch" clause in WebAppContext.doStart() that was added some time after 6.0.

I checked the servlet spec, and it doesn't clearly say what's supposed to happen in this case. I can, however, try and find out what Tomcat and WLS do.




> Regularize handling of errors on deployment such that the whole server does not necessarily fail
> ------------------------------------------------------------------------------------------------
>
>                 Key: JETTY-164
>                 URL: http://jira.codehaus.org/browse/JETTY-164
>             Project: Jetty
>          Issue Type: Bug
>          Components: Servlet
>            Reporter: Jan Bartel
>         Assigned To: Jan Bartel
>
> When an exception is thrown when deploying webapps/contexts on startup, failures may cause the server to be put into a failed state where it will return 404 for all requests. Need a way to reliably ensure that the context failures are signalled, but that the startup of the server is not impeded.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira