WAS 5.0 will not recompile JSP files

[Erian74]

After updating from WAS 4.0.2 to WAS 5.0.2 the new WAS compiles any JSP files only once. All further changes
to a JSP file are ignored - "reloading" a JSP-page inside the browser results everytime in the same (old) output.
Only stopping and restarting the appropriate AppServer makes WAS recompile the JSP... but only once again.

Looks like a caching problem to me but
* browser cache is disabled / browser configured probably
* no proxy server is involved
* dynamic caching inside WAS is disabled
* servlet caching inside WAS is disabled
* ESI caching inside plugin-cfg.xml is disabled
* making the WAR-module "reloadable" (every 3 seconds) doesn't help
* even deleting the .class files from the /temp/... directory doesn't help
* and deleting the JSP from the server!!! doesn't work as well - the (old) output is still returned, although the file
no longer exists...

Load balancing vie edge components load balancer is used but I don't think the problem is related to the balancer
(CachingProxy is not used).

Does anybody know, what the hell WAS 5.0.2 is doing? WAS 4.0.2 realized any changes to the JSP-sourcecode
without problems - why doesn't it work with WAS 5.0??? Can ClassLoaders be involved in this mystery???

Sebastian

 

[ralfpetersen99]

Were you ever able to resolve this? I'm running an application on WAS 3.5 and it is caching my jsp pages. Even when I stop/start the pages are still cached. I've also tried deleting class files, but again the old version of the pages are served. I've also double-checked my browser to make sure it's cache is empty. Any idea what I can do to remedy this?

 

[Erian74]

Yes, I was able to resolve the problem. After all, the key was the "hot deployment"-releated setting for dynamic classreloading. Unfortunately the appropriate setting for this is located in three !!! different XML-configuration files (one for the WAR, one for the EAR and one for the APP-Server itself), each of the files beeing overruled by the next file, resulting in the APP-Server XML-configuration file beeing the sole "master configuration" file.

My fault was
a) only one of the configuration files had the appropriate changes for dynamic class-reloading, while the other files didn't - they overruled my settings
b) when changing to the APP-Server configuration, additional settings have to be done in WAS 5.x in order to make this "master-configuration" take effect. I unfortunately missed this additional steps...

Anyway I'm not sure this will help you since you are using WAS 3.5 and as far as I can recall WAS 3.5 is not using XML-configuration files (I might be wrong however). Nevertheless the key to solving this problem is "hot deployment" and "dynamic class reloading" - check any available documentation files / pdf's for this terms to get an idea which settings are required.