We are experiencing a weird issue with Weblogic server 10.3.6
We are deploying custom WebCenter Portal Framework Application to Weblogic Server via the EM Console.
The structure of the servers is - We have a cluster with two managed servers on the same system. We deploy the app to the cluster itself.
The steps followed are -
- Undeploy the old app.
- Delete MDS Partition
- Clear tmp, cache folders on both managed servers.
- Restart the managed servers.
- Deploy new EAR file.
- Create new MDS partition
The ear file has a time stamp appended to the name. So on every deployment the name of the ear file is different.
The problem is - even with the above steps followed, we can see that the changes in the JSPX pages are not reflecting. We can see the changes in the Java code being reflected, but whatever changes on the JSPX pages we make are not reflected. Then randomly after multiple attempts we can see the changes.
We even tried clearing tmp on the AdminServer and restarting.
Now the solution we tried was - During build time we are invoking weblogic.appc and compiling the jspx pages and packaging the generated servlets with the ear file itself. For the first couple of times it worked but then the same issue appeared again. May be it worked randomly, not sure about that.
One more thing is that if you go to the tmp folder on the managed servers and decompile the servlet class generated, they have old code, but if you decompile the servlet classes in the ear file we can see the changes, since the jspx pages are manually compiled.
We also tried the precompile and page check seconds option in weblogic.xml but to no avail.
We are not able to figure out from where the weblogic server is picking the old code. If we do a locate for any of the jspx pages on the server, we find them only in the tmp folder.
Any help would be appreciated.
When you deploy your application to wls it first copies the installation to a stage folder and then distribues it to the managed servers for deployment. At the time of deployment each managed server expands the files as needed.
check in the stage folder for the presence of older versions of the files.
also in your steps instead of undeploying delete the app.
usually stage folder contents is the culprit. When you undeploy and redeploy wls does not delete the files from stage to save on time.
This is cache issue. Rebounce the entire environment, after you build the file again with changes make sure about the deployment part.
If managed servers are in different machines, plz make sure you deploy it correctly and there are no network issues.
Have you cleared all the cache and tmp even for all the managed servers.
How are you deploying the app?
Using console or any other?
Thanks for the response. The deployment steps are mentioned in the OP. Yes we clear cache and tmp folders on all the managed servers! We are deploying the app through the Enterprise Manager Console. Cannot deploy a Portal App via the Admin Console as the app requires MDS configs.
I know this is weird. We have no idea where the server is picking the files from!