How to clean the jsp cache in WebSphere

This article mainly introduces how to clean up the jsp cache in WebSphere, which has a certain reference value. Interested friends can refer to it. I hope you will learn a lot after reading this article.

When deploying the system under websphere, no matter restart the application or node service, it will not take effect after modifying the .xml file under the application. Generally speaking, standard file updates can be replaced by applying updates, such as "Enterprise Application"-> Select Application-> "Update" to keep the results of the configuration file consistent with the directory in ear, and then upload the restart service directly to complete the update.

Another way is to find the configuration file you want to change, such as web.xml, under {was_home}\ AppServer\ profiles\ AppSrv01\ config\ cells\ dwCell01\ applications\ {App} .ear\ deployments, and then restart the service.

As a tip, JSP cache cleanup can be done by deleting {was_home}\ AppServer\ profiles\ AppSrv01\ temp\. I have encountered a very stubborn cache, and I can't get rid of it, and there are three ways to do it in the end:

1. Upgrade the minor version of was to the latest

2. Reinstall the application

3. Access the connection with a random number

Or it's okay.

Clear the .class file in the cache and then refresh it. If there is still no response, restart Websphere will take effect. Another way is to delete or rename the jsp from the project, and then go to the browser to view the page. At this time, you may report an error, and then add or change the name of the corresponding jsp. When you check the application in the browser again, you will find that the update effect of this jsp has come out.

Solution:

Find the following file

/ home/wasuser/WebSphere/profiles/AppSrv02/config/cells/kmapp07Cell01/applications/KMPortal_war.ear/deployments/KMPortal_war/KMPortal.war/WEB-INF/ibm-web-ext.xmi

Open the ibm-web-ext.xmi file under / WEB-INF/, and the original ibm-web-ext.xmi file is as follows:

The red part is added, and the reloadEnabled property is set to true. After setting it, you must restart the Websphere to take effect.

Other properties that can be set are similar to:

Thank you for reading this article carefully. I hope the article "how to clean up the jsp cache in WebSphere" shared by the editor will be helpful to everyone. At the same time, I also hope that you will support and follow the industry information channel. More related knowledge is waiting for you to learn!