Problem
Received the following error from Websphere7.
Solution
Go to the application installation path under Websphere. e.g.
Check the
In my case, the servlet-name element was missing. This is because I mapped it to a servlet-name which didn't exist.
Received the following error from Websphere7.
[7/06/11 12:48:47:093 EST] 0000001e filter W com.ibm.ws.webcontainer.filter.WebAppFilterManager getFilterChainContents SRVE0307W: null mapping for filter. This may occur if you try to specify a * mapping on a pre-2.5 app.
[7/06/11 12:48:47:124 EST] 0000001e webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[/WEB-INF/views/500.jsp]: java.lang.IncompatibleClassChangeErrorSolution
Go to the application installation path under Websphere. e.g.
%was_home%\AppServer\profiles\AppSrv01\installedApps\YourHostNode01Cell\YourApp.ear\YourApp.war\WEB-INFCheck the
web_merged.xml for any servlets without a url-pattern mapping. (web_merged.xml has been created by WAS, from the app's web.xml).In my case, the servlet-name element was missing. This is because I mapped it to a servlet-name which didn't exist.
Thanks for sharing it. I had the same problem; your post helped solving it.
ReplyDeleteHi Nick,
ReplyDeletePlease help me understand why this file is getting created by web sphere when a web.xml is already available in my the deployment.
Also please go through my scenario and provide valuable inputs
I have an application of which I create a ear and try to deploy the same in Websphere 7.0.0.9,7.0.17,7.0.0.21. On deployment the console hangs for a long time and does not come up.
I tried to refresh the screen and kill the IE process.When i relogin into the console and check for the application status I see the same is down.Even after repeated attempts of bring it up it is not happening.
For the sake of trying I bring the web sphere profile down and then the profile itself goes down due to java.lang.OutOfMemoryError.
I have gone through some posts and added the entry in my web.xml (metadata-complete="true") after this the server starts working as expected.
1.Please help me understand why the web_merged.xml gets generated and how is it affecting my application.
2.The recent change that we have done is to upgrade the xml version to 2.5. Id that the reason for getting an out of memory exception?
3.Any remedies instead of the above workaround are possible?
(reason why I am asking this is even if i am adding this tag in my web.xml prior to building the war,on deployment the tag in the web.xml is not present while the merged counterpart gets generated. As such which i have to directly edit files in my deployed area)
My mail id is raghav.silicon@gmail.com
Thanks & Regards,
Raghav