[
https://issues.apache.org/struts/browse/WW-1526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41171
]
Kishore Senji commented on WW-1526:
-----------------------------------
I think I ran in to this issue. In addition to flushing the output stream you
could also try closing the output stream which I guess resolves the issue on
all the WebSphere versions. WebSphere also had a strange Filter bug where a
filter was not invoked for a url which ends in a .jsp which can end up in to a
404 in the .jsp file does not really exist. I hope they have fix this in the
future versions.
> Error with handling static resources under WebSphere 6
> ------------------------------------------------------
>
> Key: WW-1526
> URL: https://issues.apache.org/struts/browse/WW-1526
> Project: Struts 2
> Issue Type: Bug
> Affects Versions: 2.0.1
> Environment: IBM WebSphere 6.0
> Reporter: Adam Czysciak
> Assignee: Ted Husted
> Fix For: 2.0.7, 2.1.0
>
>
> It seems to be a bug with WebSphere, but a tiny patch to Struts2 can fix it.
> The findStaticResource method of FilterDispatcher calls copy(), then closes
> the InputStream. It works well for static resources bigger than 4kb, bit it
> fails with "cannot obtain output stream" forsmaller files.
> The patch is very simple: call output.flush() at the end of copy() method.
> Works perfect with WebSphere 6.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
