May 10 10
If you use ServletFilters that are mapped to URLs/resources that don’t physically exist (e.g. such as Paul Tuckey’s UrlRewriteFilter) IBM WebSphere 6.1 will answer such requests with “Error 404: SRVE0190E”. If WebSphere runs in trace mode you’ll see a FileNotFoundException in the log file.
This is yet another idiotic WebSphere behavior that you need to work around. Set
com.ibm.ws.webcontainer.invokefilterscompatibility=true
in Servers -> Server -> Web Container Settings -> Web Container -> Custom Properties.
IBM has more information in their custom properties documentation (search for “Invoking the filter capability”) and on the respective support document (for fix pack 6.1.07). Since the URLs to those documents might become invalid in the future I persisted the latter in a PDF.
August 3rd, 2010 at 0:15
Thank you for this … but there is one error in your post. The custom property that you have suggested; is actually in camel case. com.ibm.ws.webcontainer.invokeFiltersCompatibility
August 3rd, 2010 at 22:58
IBM isn’t consistent in its documents…sometimes it’s camel case and sometimes it’s not. I can confirm that it doesn’t seem to make any difference. I noticed that our development system has the property all lower case and it still works.
October 14th, 2010 at 19:59
Wow, It is working…. Thank you so much…..
October 29th, 2010 at 10:02
Awesome!!! Thanks a ton for such a clear picture of the resolution this issue!!!
November 4th, 2010 at 19:46
Also many thank for this clear solution description! Helps a lot!
December 24th, 2010 at 16:09
Many thanks for the solution! Saved a lot time. Websphere sucks by the way.
January 8th, 2011 at 16:54
[...] We got a SRVE0190E error as we tried to access the maint.xhtml. This could be solved by performing the steps which are described here (Websphere property). [...]
March 16th, 2011 at 21:34
Great resolution, Thank you so much!!!
June 11th, 2011 at 12:56
this doen’t solved our problem. Any more suggestions???