• 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
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

Dynamic Reloading issues in WAS EX 6.01

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

We have a WAR(no EJBs) deployed on a WebSphere Express 6.0 on a Win2003 platform. We have a new upgrade to our software out, so we tried taking advantage of the dynamic reloading option and just copy/pasted all the JSPs and classes in to their respective folders (overwriting the previous versions). Just to be safe, I also stopped and started the WebSphere Service.

The issue is that the new code does not get picked up despite stopping and starting the WebSphere service. We have Dynamic Reloading Enabled (=true). Reload interval is set to 14400 secs. Is this interval too long? Should it not pick up the new code once the service is restarted?

We also tried deleting all the old JSPs and classes and copying just the new ones. Then restarted the service...it still picks up the older versions of code..........from a cache somewhere perhaps??

Any suggestions?



Thanks
V
 
Veni Velkoor
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Any ideas?

Thanks
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
not sure about WAS 6, but in 5.1.x we explicit had to remove the files in the temp dir ([WAS_ROOT]/temp) to avoid start up failures and/or strange behavior;

by providing a custom JVM-property we succeeded in automating this step (bug in WAS 5.1.x)
 
If I'd had more time, I would have written a shorter letter. -T.S. Eliot such a short, tiny ad:
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
reply
    Bookmark Topic Watch Topic
  • New Topic