• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

Does Webshpere App Server 6.1 cache jar files?

 
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

Does anyone know if Webshpere App server 6.1 caches jar files? If so where are they cached? I know where it caches jsp files.

Thanks,
Rich
 
author and cow tipper
Posts: 5006
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
WebSphere just loads the class files into memory.

An ear file is extracted and the files are placed uncompressed on the file system. But that's more temporary storage than a cache.

Are you having a ClassNotFoundException or something of the sort? Changes not being incorporated after deployment?

-Cameron McKenzie
 
Richard Vagner
Ranch Hand
Posts: 108
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Cameron McKenzie,

Thanks for your reply.

Our Websphere app server has recently been upgraded to version 6.1.0.21 on both Dev and QA. One of our apps on DEV failed after the upgrade -- I should say the app was ok initially after the server upgrade and the problem only occurred after we edited an simply jsp page and redeployed the app to the DEV server. We found that an older version of a jar file causes the problem in upgraded server environment and problem resolved after we replace the jar file with a new one.


So after QA server was upgraded to the version 6.1.0.21, I expected that app on QA to fail because of that jar file. But it didn't fail. I have the same package (old jar file in it) redeployed to QA server and the app still worked. I am a bit puzzled by that. That is why I am wondering if cache may play a part in this?

Thanks a lot,
Rich
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic