May 10 10

Solution to “Error 404: SRVE0190E” on WebSphere 6.1

Java, Software Development Add comments

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.

2 Responses to “Solution to “Error 404: SRVE0190E” on WebSphere 6.1”

  1. Ameya Says:
    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

  2. frightanic Says:
    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.

Leave a Reply