[jira] [Updated] (HADOOP-7703) WebAppContext should also be stopped and cleared

["Alejandro Abdelnur (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HADOOP-7703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alejandro Abdelnur updated HADOOP-7703:
---------------------------------------

    Fix Version/s:     (was: 3.0.0)
                   2.2.0-alpha

Committed to branch-2
                
> WebAppContext should also be stopped and cleared
> ------------------------------------------------
>
>                 Key: HADOOP-7703
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7703
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.24.0
>            Reporter: Devaraj K
>            Assignee: Devaraj K
>             Fix For: 2.2.0-alpha
>
>         Attachments: HADOOP-7703.patch
>
>
> 1. If listener stop method throws any exception then the webserver stop method will not be called
> {code}
> public void stop() throws Exception {
>     listener.close();
>     webServer.stop();
> }
> {code}
> 2. also, WebAppContext stores all the context attributes, which does not get cleared if only webServer is stopped.
> so following calls are necessary to ensure clean and complete stop.
> {code}
> webAppContext.clearAttributes();
> webAppContext.stop();
> {code}
> 3. Also the WebAppContext display name can be the name passed to HttpServer instance.
> {code}
> webAppContext.setDisplayName(name);
> {code}
> instead of
> {code}
> webAppContext.setDisplayName("WepAppsContext");
> {code}

--
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