We have a situation where we restart the Weblogic server when we place new code into the Deploy area (server set to no-deploy mode) which is fine as long as we move forward.
Recently we had need to regress the code to back out the new release. We placed the old code in teh deploy area and restarted and ended up with very weird results.
Our log files indicated that we were in fact still running the new code.
Clearly the Weblogic server had cached some compiled versions of JSPs etc, but upon restart these were still seen as newer than the (now regressed) code.
We ended up having to do a 'touch' of all the files to force it to accept the regressed code as 'new'. Not very elegant.
Does anyone know of a 'nice' way to do this (e.g. a command line, or a cache dir that can be deleted)?
I note that under the server's dir their is a hidden dir called .wlnotdelete which seems to be updated with recent files????
Recently we had need to regress the code to back out the new release. We placed the old code in teh deploy area and restarted and ended up with very weird results.
Our log files indicated that we were in fact still running the new code.
Clearly the Weblogic server had cached some compiled versions of JSPs etc, but upon restart these were still seen as newer than the (now regressed) code.
We ended up having to do a 'touch' of all the files to force it to accept the regressed code as 'new'. Not very elegant.
Does anyone know of a 'nice' way to do this (e.g. a command line, or a cache dir that can be deleted)?
I note that under the server's dir their is a hidden dir called .wlnotdelete which seems to be updated with recent files????