[
https://issues.apache.org/jira/browse/HADOOP-4695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated HADOOP-4695:
----------------------------------
Assignee: Kan Zhang
Status: Open (was: Patch Available)
I don't understand the fix (or the problem). According to
[this|http://jetty.mortbay.org/jetty5/doc/servlet24.html#d0e321] documentation
discussing the Jetty5 filter mapping, it's possible for the same filter to get
applied more than once. It sounds like the burden is on the servlet author and
not necessarily the filter configuration, so perhaps the correct fix is to the
test case. Ignoring the filter chain does sound extreme, though, particularly
if the double-filtering case happens in error states. Is it reasonable to wait
and see if this is reproducible in Jetty6?
> TestGlobalFilter.testServletFilter fails
> ----------------------------------------
>
> Key: HADOOP-4695
> URL: https://issues.apache.org/jira/browse/HADOOP-4695
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Kan Zhang
> Attachments: 4695-0.patch, 4695-1.patch
>
>
> {noformat}
> junit.framework.AssertionFailedError: expected:<14> but was:<15>
> at
> org.apache.hadoop.http.TestGlobalFilter.testServletFilter(TestGlobalFilter.java:150)
> {noformat}
> For more details, see
> http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/666/ .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
