We used a shared SAN, so all instances of Coldfusion were looking at the same code, and then had shell scripts that would ssh into the boxes and restart the appropriate Coldfusion instances.
I have also seen instances in which code is mirrored on each box, using rsync, or shell scripts to push the code out to the boxes. The push scripts would contain the restart commands, so that the server would be restarted once the new code was in place. speeves On Wed, Jun 17, 2009 at 10:51 AM, Donnie Carvajal < donnie.carva...@transformyx.com> wrote: > > My applications are hosted on multiple servers and I am storing several DAO > components in the Application scope. Basically, whenever a change is made > to any component that is stored in the Application scope and we deploy to > the server farm, I have to restart the application on each server (basically > run a web page for a URL specific to each server). > > What is the common practice out there for updating an application on a > server farm and restarting the application to refresh the application scope > components? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:323581 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
