• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WAS 5.0 will not recompile JSP files

 
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
[ July 31, 2003: Message edited by: Sebastian Krzyzanowski ]
 
Ranch Hand
Posts: 365
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
What about deleting them from <WAS_HOME>/temp directory? Delete these and then that should force WAS to recomplie. Have you tried this?
 
Sebastian Krzyzanowski
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
As you can see above - I've tried this too :-(
 
Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
Isn't a "ADMA5004E" message recorded in WASPostUpgrade log file in your environment?
If so please see below.
http://www-1.ibm.com/support/docview.wss?uid=swg21111129
 
Sebastian Krzyzanowski
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I made it work - finally.
Please see http://www-106.ibm.com/developerworks/forums/dw_thread.jsp?forum=266&thread=13224&cat=9
for further information.
Thanks,
Sebastian
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic