Geek Answers Handbook

Weblogic does not clear cache

We installed Weblogic 10.3.1.0 on an RHEL machine (linux).
Recently, a new version of the application has been uploaded to Weblogic. Unfortunately, the new changes do not reflect. The environment team reported that before deploying, they cleared the /opt/BAE_Weblogic/WL_DOMAIN/servers/AdminServer/tmp/_WL_user/our_application .

I checked the following folders and I do not see old files there:

 /tmp/_WL_user/AFM2.2.24M2/ths7y1/war /tmp/_WL_user/AFM2.2.24M2/ths7y1/public domains/DOMAIN/servers/AdminServer/cache

Is there something that I am missing.

+4
source share
2 answers

Do not delete the tmp/_WL_user/appname/ before deploying the new version; delete it after deployment, if necessary.

Better yet, do something in writing / create your application so that the new WAR/EAR/JAR/TRUCK/BICYCLE files contain only files with newer timestamps.

Even better, there is a file that, if it exists in WEB-INF or META-INF (don’t remember which one), when you access WebLogic the first time after re-deployment it will see that this file has a newer timestamp and will automatically hide the entire cache -Ore. The problem is that I don’t remember what this file name should look like (IIRC, this is in ALL CAPS, though).

But even better, rewrite the application (s) so that this is not a problem. Of the several hundred applications that I run here on WebLogic servers, only a very small number have ever encountered this problem. The vast majority of Just Work applications, when they are updated,

NTN.

+3
source

I just met a similar problem when I did not get my new classes during the MDB call. I restarted the servers, deleted the deployment items, believing that it can clear the cache, however the folders available for deployment are available in / tmp / _WL_user // war, / tmp / _WL_user // public, domains / DOMAIN / servers / AdminServer / cache, but with no luck.

But then I realized that by mistake I put these classes (OLD) in one of the jars. These classes actually posed a problem, and I thought weblogic was caching files. It sounds a little silly, but it can help if someone makes a similar mistake :-)

Cheers, Mayur

0
source

More articles:


All Articles