WAS Upgrade to v8.5.5.12 - DMGR console not working !!!

       After successful upgrade of WAS from v8.5.5.10 to v8.5.5.12, and successfully restarting DMGR/nodeagents/Application Servers, when was trying to access the DMGR console url: https://<hostname>:<port>/ibm/console/login.do and after successful login, was getting Error: 500 - Servlet Exception. Below was the error summary:

Original Exception:
Error Message: java.lang.NoSuchMethodError: com/ibm/ws/webcontainer/webapp/WebAppConfiguration.isEncodeDispatchedRequestURI()Z

Error Code: 500
Target Servlet: 
Error Stack: 
java.lang.NoSuchMethodError: com/ibm/ws/webcontainer/webapp/WebAppConfiguration.isEncodeDispatchedRequestURI()Z 
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:1241) 
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:195) 
     at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:681) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) 
     at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistance(WSCUrlFilter.java:982) 
     at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:514) 
     at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:335) 
     at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107) 
     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3951) 
     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) 
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1014) 
     at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817) 
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) 
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463) 
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530) 
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316) 
     at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88) 
     at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1820) 
     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) 
     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) 
     at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) 
     at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) 
     at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) 
     at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) 
     at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) 
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892) 
     



Error Page Exception:
Error Message: java.lang.NoSuchMethodError: com/ibm/ws/webcontainer/webapp/WebAppConfiguration.isEncodeDispatchedRequestURI()Z

Error Code: 500
Target Servlet: 
Error Stack: 
java.lang.NoSuchMethodError: com/ibm/ws/webcontainer/webapp/WebAppConfiguration.isEncodeDispatchedRequestURI()Z 
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:1241) 
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:195) 
     at com.ibm.ws.webcontainer.webapp.WebApp.sendError(WebApp.java:3411) 
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:1432) 
     at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:195) 
     at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:681) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:136) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:97) 
     at com.ibm.ws.console.core.servlet.WSCUrlFilter.setUpCommandAssistance(WSCUrlFilter.java:982) 
     at com.ibm.ws.console.core.servlet.WSCUrlFilter.continueStoringTaskState(WSCUrlFilter.java:514) 
     at com.ibm.ws.console.core.servlet.WSCUrlFilter.doFilter(WSCUrlFilter.java:335) 
     at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:195) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:91) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:967) 
     at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1107) 
     at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3951) 
     at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304) 
     at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:1014) 
     at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1817) 
     at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:200) 
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:463) 
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:530) 
     at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:316) 
     at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:88) 
     at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1820) 
     at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) 
     at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) 
     at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) 
     at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) 
     at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) 
     at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) 
     at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) 
     at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)


This basically means that after upgrade there has been some problem while loading the latest class caches. It is still referencing the old class cache/libraries.

To resolve the issue, please follow the below steps:

1) To clear the OSGi class cache:
For UNIX platforms, run the following script in each profile: 
<WebSphere_HOME>/profiles/profile_name/bin/osgiCfgInit.sh 

For Windows platforms, run the following script in each profile: 
<WebSphere_HOME>\profiles\profile_name\bin\osgiCfgInit.bat

2) To clear the JVM's class cache (Linux, AIX, z/OS and Windows) :

For UNIX and z/OS platforms, run the following script: 
<WebSphere_HOME>/bin/clearClassCache.sh 

For Windows platforms, run the following script: 
<WebSphere_HOME>\bin\clearClassCache.bat
Note - You should not delete the cache while any of the JVM's are running and using the cache. The server has to be stopped before clearing the cache. 

3) Clear contents under the javasharedresources folder:
<WinUsers_home>\Local Settings\ApplicationData\javasharedresources\ 
UNIX - /tmp/javasharedresources 
After this, please start DMGR and try to access DMGR console. This will permanently fix the issue.

For further details regarding temp files/caches etc, please visit this technote: 
     

Comments

Post a Comment

Popular posts from this blog

CRIMA1020E: Installation Manager Throws Error While Applying WAS Fixpack v8.5.5.12 !!!

While upgrading WAS to fixpack 8.5.5.12, Installation Manager throws many CRIMA1020E errors. Some of the errors are mentioned below in the failed upgrade logs: Error during "install" phase:                                             CRIMA1020E: Failed to extract zip                                     com.ibm.websphere.ND.ndonly_027_all.all 8.5.5012.201706271504. File     /apps/app/IBM/WebSphere/AppServer/properties/messages/en/com.ibm.datapow er.dmi.messages.xml already exists.                                                                             ...
Read more

CRIMA1020E: WAS Re-install Steps !!!

Here are the steps to re-install WAS in UNIX after all the other options to upgrade has failed. Please refer to my earlier blog:  CRIMA1020E - Resolution Steps A. Backup following directories for safety reason: WAS installation directory, Installation Manager shared resource directory , Agent data directory You can check the following URL for agent data location: Agent data location B. Run profile_root/bin/backupConfig for all profiles to backup the profile configuration Don't forget to move generated zip files out of WAS directory. backupConfig command C. Noted down all profiles' name in old installation D. Uninstall WAS 8.5.5.10 There will be some files left behind after uninstalling, please also remove them manually. E. Install and upgrade to WAS 8.5.5.10 and all fixes as previous installation Install to the same location as before. F. Create profiles as you had previously with the WAS 8.5.5.10 installation Those profiles are dummy profile, and t...
Read more