WebSphere Cache Issues

First, the scene:
∷∷ Linux environments with WebSphere control updates, but due to business requirements, all updates must be revoked. Therefore, I deleted the corresponding application directory and archived the backup file, and I found that it was different from the expected effect.

∷∷ by repeatedly confirming the code yes, finally did some other tests, but still did not solve the problem!

• Solution:

∷∷ originally because the WebSphere cache file is causing, when you deploy the application, the Web. XML is cached to the following directory:

 /app/WebSphere/AppServer/profiles/AppSrv01/config/cells/YDZYTNode01Cell/applications/......

(not suitable for all systems, it is presented here for easy access to the same problem in the future); Find Web. XML Delete

Special attention:

∷∷ The above solution only applies to changes to the Web. xml file after the update is submitted, if the JSP effect is inconsistent with the expected, you will need to locate the following directory:
∷∷ WebSphere JSP compiled as class cache directory

The Deployment directory is:

/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/MBSITAPPCell01/mobilebank1_war.ear/mobilebank1.war

The corresponding class cache directory is:

/usr/IBM/WebSphere/AppServer/profiles/AppSrv01/temp/MBSITAPPNode01/server1/mobilebank1_war/mobilebank

config/cells/host name/applications/root. ear/deployments/root _war/root. war/web-inf/web.xml
Such as:

/app/WebSphere/AppServer/profiles/AppSrv01/config/cells/YDZYTNode01Cell/applications/...

WebSphere Cache Issues