struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nils-Helge Garli (JIRA)" <j...@apache.org>
Subject [jira] Commented: (WW-2523) NPE in dispatcher cleanup when FilterDispatcher is used in a portlet
Date Thu, 16 Oct 2008 04:32:37 GMT

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

Nils-Helge Garli commented on WW-2523:
--------------------------------------

I think the best would be if the FilterDispatcher and the Jsr168Dispatcher had it's own actual
instance of the Dispatcher. I'm not sure how easy that is to achieve though.

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


Mime
View raw message