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.
How to work around SRVE0190E
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 about SRVE0190E and invokefilterscompatibility=true 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.
Update 2012-10-14
Although my post specifically says WebSphere 6.1 I keep getting request about SRVE0190E for WebSphere X.Y. I don’t know anything about anything other than 6.1 as I try my best to stay away from anything WebSphere-related as far as I can. However, others claim that for the same problem in WebSphere 8 (I didn’t say 7 or 9 or whatever) the settings need to be
com.ibm.ws.webcontainer.mapFiltersToAsterisk=true com.ibm.ws.webcontainer.removetrailingservletpathslash=true com.ibm.ws.webcontainer.invokeFiltersCompatibility=true
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
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.
Wow, It is working…. Thank you so much…..
Awesome!!! Thanks a ton for such a clear picture of the resolution this issue!!!
Also many thank for this clear solution description! Helps a lot!
Many thanks for the solution! Saved a lot time. Websphere sucks by the way.
Great resolution, Thank you so much!!!
this doen’t solved our problem. Any more suggestions???
It worked. thanks a lot. we can use below link to set the value in RAD7.5
http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rweb_custom_props.html
I also stuck in this problem.
I am creating a web application with spring/GWT/hibernate.
I installed it on WebSphere Application server 8.5 (for developers).
After configuring the property “com.ibm.ws.webcontainer.invokefilterscompatibility=true” for server as mentioned in this post
I am still getting below error for a GWT rpc call. (File not found: /trainingmanagement/rpc/gwtuserservice)
[25/8/12 22:22:16:833 IST] 0000006e filter E com.ibm.ws.webcontainer.filter.FilterInstanceWrapper service SRVE8109W: Uncaught exception thrown by filter springSecurityFilterChain: java.io.FileNotFoundException: SRVE0190E: File not found: /trainingmanagement/rpc/gwtuserservice
I deleted all your configuration, sorry. It’s not relevant to the problem as far as I can tell.
Note that this explanation is for WAS 6.1 specifically. IBM might have changed the property name in newer versions.
Thanks for your help ..
Setting this property for File Not Found error helped in WAS 7.0.0.23 also:
com.ibm.ws.webcontainer.invokeFiltersCompatibility=true
Still not working, we are getting beloe error in FFDC logs. Could you please help me on this..
[5/14/13 13:46:50:953 MST] FFDC Exception:java.io.FileNotFoundException SourceId:com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters -IOE ProbeId:1044
java.io.FileNotFoundException: CWSRV0190E: File not found: /testserviceWS
at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor._processEDR(DefaultExtensionProcessor.java:893)
Sorry, really cannot help you.
HI Marcel,
After setting com.ibm.ws.webcontainer.invokeFiltersCompatibility=true in websphere 7.0.0.11 still i am getting Error 404: SRVE0190E: File not found: /indexAction.action . Please let me know the solution how can i reslove this.
Did you read the entire post? I clearly stated that I don’t know anything about WebSphere versions other than 6, sorry. However, there is a comment from ‘Prabhakar’ from January 2013 just above which says that setting com.ibm.ws.webcontainer.invokeFiltersCompatibility=true workes for WAS 7.0.0.23.
Thanks a lot, Appreciate your effort.. i struggled one week before i get to this post.. I got the same problem in webshpere 7.0.0.23. After adding the property , need to redeploy the application. Then it starts working..!
Thank you a lot , this post help me. I has problems on was 6.1
Do I need to redeploy the application after making these changes in WAS to make it work?
No, but you may need to restart the container or the entire server.
I still face the Problem on WAS 9.0, FileNotFound not able to hit the defined context in WAS