Comments on: Solution to “Error 404: SRVE0190E” on WebSphere 6.1

By: jyothi

jyothi — Sat, 11 Jun 2011 10:56:47 +0000

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

By: Pandu

Pandu — Wed, 16 Mar 2011 19:34:36 +0000

Great resolution, Thank you so much!!!

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

Sat, 08 Jan 2011 14:54:43 +0000

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

By: Kevin

Kevin — Fri, 24 Dec 2010 14:09:23 +0000

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

By: Michael Er

Michael Er — Thu, 04 Nov 2010 17:46:48 +0000

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

By: Sachin

Sachin — Fri, 29 Oct 2010 08:02:59 +0000

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

By: Vijayaraj

Vijayaraj — Thu, 14 Oct 2010 17:59:17 +0000

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

By: frightanic

frightanic — Tue, 03 Aug 2010 20:58:48 +0000

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.

By: Ameya

Ameya — Mon, 02 Aug 2010 22:15:15 +0000

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