WebLogic Clearing the cache

Background: When developing debugging or testing, it is often time to re-update the deployment service to see if some updates are not reflected, or if the previous situation, or other error issues, it is necessary to consider that the WebLogic cache may not be cleaned up.

You can try this first:

If you publish to a WebLogic project, the login discovery or the original code error, you can try to clean up the WebLogic cache:
1. Stop the app in the WebLogic console, remove the deployed project
2. Log in to the WebLogic server and delete the Shgfmis directory in the following directory:

D:\bea\user_projects\domains\shgfmis\servers\AdminServer\tmp\_WL_user

D:\bea\user_projects\domains\shgfmis\config\deployments

The development environment removes the Shgfmis directory under the following directory:

D:\bea\user_projects\domains\shgfmis\servers\AdminServer\tmp\_WL_user

D:\bea\user_projects\domains\shgfmis\config\deployments

3. Redeploy the project

"Note": Where Shgfmis is the name of my project

Such as:

CD Weblogic/user_projects/domains/yypt_domain/servers/yypt_adminserver/tmp/_wl_user

Rm-r Yypt

Delete Yypt Cache

Then restart WebLogic

If this method still doesn't work, try the following to clear all the caches:

The cleanup cache steps are as follows:

1. Pre-condition: Stop service

2, find the following 3 directories, and then delete the files inside can be:

.../user_projects/domains/base_domain/servers/adminserver/tmp/
.../user_projects/domains/base_domain/servers/adminserver/cache/
.../user_projects/domains/base_domain/config/deployments/

Note: In the cache directory, if the security folder is found, the folder is a secure authentication file and cannot be deleted. Typically, a service that tests the pattern generates the file automatically, while the production pattern is created by the person.

3, restart the service can be completed

WebLogic Clearing the cache