[
https://issues.apache.org/struts/browse/WW-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44849#action_44849
]
Torsten Krah commented on WW-2523:
----------------------------------
Yes this would be the best idea. JBoss is doing undeployment first for
FilterDispatcher, so you have to patch Jsr168 one too ... that can't be the
right solution.
However i don't know how to patch both so everyone got its own actual instance,
if someone can provide me with some more details how it might be done, i might
be able to write a patch.
> 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
>
> Attachments: FilterDispatcher.diff, stackTrace_failure.txt,
> stackTrace_ok.txt
>
>
> 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.
