[
https://issues.apache.org/struts/browse/WW-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46117#action_46117
]
Nils-Helge Garli commented on WW-2523:
--------------------------------------
It's still beyond my understanding how the 'instance' thread-local variable
suddenly turns null... I have tried doing a null check, but aparently the
'dispatcherListeners' static variable is also suddenly null. So for some
reason, the static fields of the class are set to null somewhere... I'm
guessing there's some sort of cleanup happening in the container that causes
this.
> 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.
