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.

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

  1. Ameya Says:

    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:

    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.

  3. Vijayaraj Says:

    Wow, It is working…. Thank you so much…..

  4. Sachin Says:

    Awesome!!! Thanks a ton for such a clear picture of the resolution this issue!!!

  5. Michael Er Says:

    Also many thank for this clear solution description! Helps a lot!

  6. Kevin Says:

    Many thanks for the solution! Saved a lot time. Websphere sucks by the way.

  7. Seam, Websphere 6.1 and ‘Error 404: SRVE0190E: File not found’ | systemfeld Says:

    [...] 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). [...]

  8. Pandu Says:

    Great resolution, Thank you so much!!!

  9. jyothi Says:

    this doen’t solved our problem. Any more suggestions???

Leave a Reply