You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Rainer Hermanns (JIRA)" <ji...@apache.org> on 2006/12/06 20:28:57 UTC

[jira] Resolved: (WW-1542) Jsr168Dispatcher does not destroy the Dispatcher properly

     [ http://issues.apache.org/struts/browse/WW-1542?page=all ]

Rainer Hermanns resolved WW-1542.
---------------------------------

    Fix Version/s: 2.0.2
       Resolution: Fixed

Thanks for the patch suggestion.
Added to SVN as rev 483185 

> Jsr168Dispatcher does not destroy the Dispatcher properly
> ---------------------------------------------------------
>
>                 Key: WW-1542
>                 URL: http://issues.apache.org/struts/browse/WW-1542
>             Project: Struts 2
>          Issue Type: Bug
>    Affects Versions: 2.0.1
>            Reporter: Rickard Öberg
>         Assigned To: Rainer Hermanns
>             Fix For: 2.0.2
>
>
> Jsr168Dispatcher does not implement destroy(), where it should clean up the Dispatcher instance. The result is that the threadlocal reference to the Dispatcher is never cleared, and so a portlet app can never be redeployed properly.
> Add this to Jsr168Dispatcher to fix it:
> public void destroy()
> {
>    if (dispatcherUtils == null) {
>       LOG.warn("something is seriously wrong, DispatcherUtil is not initialized (null) ");
>    } else {
>        dispatcherUtils.cleanup();
>    }
> }

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