[jira] Issue Comment Edited: (WW-2523) NPE in dispatcher cleanup when FilterDispatcher is used in a portlet

["Torsten Krah (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/struts/browse/WW-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44555#action_44555 ] 

tkrah edited comment on WW-2523 at 10/8/08 1:15 AM:
-----------------------------------------------------------

This is a issue to with Pluto 1.1.5 and e.g. Tomcat 6.0.13 and Pluto 1.1.6 with Tomcat 6.0.18.
I am facing this problem too on JBoss (4.0.5, Tomcat 5.5.20, Liferay 5.x).

Version 2.0.11.2 (latest stable Release) is affected too.
I think this is a critical flaw as you cannot undeploy or redeploy the webapp and are forced to restart the container every time.
Imho this should be fixed in 2.0 branch too.

      was (Author: tkrah):
    This is a issue to with Pluto 1.1.5 and e.g. Tomcat 6.0.13 and Pluto 1.1.6 with Tomcat 6.0.18.
I am facing this problem too on JBoss (4.0.5, Tomcat 5.5.20, Liferay 5.x).
  
> NPE in dispatcher cleanup when FilterDispatcher is used in a portlet
> --------------------------------------------------------------------
>
>                 Key: WW-2523
>                 URL: https://issues.apache.org/struts/browse/WW-2523
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Dispatch Filter, Plugin - Portlet
>    Affects Versions: 2.0.11, 2.1.0
>         Environment: JBoss Portal 2.6.4, Struts 2.1.1
>            Reporter: Nils-Helge Garli
>             Fix For: Future
>
>
> When the FilterDispatcher is configured in web.xml, it does cleanup first, then JSR168Dispatcher does cleanup, and for some reason, the ThreadLocal variable (the actual ThreadLocal variable, not the value it contain) is null. I don't know if this is an issue only in JBoss.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.