> > Not if it is in a 'hot deploy' directory is my understanding (this has > > been discussed here before but I don't recall the exact details).
Where is the 'hot deploy' directory? Joe > -----Original Message----- > From: Dick Applebaum [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, November 26, 2002 11:12 PM > To: CF-Talk > Subject: Re: CFMX Server -Java class > > > On Tuesday, November 26, 2002, at 07:31 PM, Sean A Corfield wrote: > > > On Tuesday, Nov 26, 2002, at 16:31 US/Pacific, Dick Applebaum wrote: > >> You recompile a Java class file that is referenced by cfobject. > >> > >> I am told that you must recycle CFMX for the updated class file to be > >> recognized. > > > > Not if it is in a 'hot deploy' directory is my understanding (this has > > been discussed here before but I don't recall the exact details). > > > > They drop and restart each server in the cluster. Normally production > > systems do not use 'hot deploy' because of the performance overhead > > involved in 'watching' a hot deploy directory. > > > > OK, then it would seem to make sense to use "hot deploy"on a developer > system > where the performance overhead would not be an issue. > > Then, on a single-server production system, not use "hot deploy". > > > >> What about CFMXj2ee running on JRun, webSphere, ant the like? > > > > See above for clusters - some of those systems support session > > replication / failover. That means zero downtime for this sort of > > upgrade. > > So, with session replication/failover, you: > > 1) recompile the necessary Java class files and deploy them on all > the servers (they remain inactive). > > 2) recycle each server, one-at-a-time, activating the updated class > files > > It could get messy if the old Java classes were causing failures and/or > you had other > failures when recycling the individual servers -- but this would be > unlikely. > > At best, you wouldn't even notice. > > At worst, you could recycle the whole system, > > > > >> What about Pure Java/JSP systems on these app servers? > > > > Same. > > > > So, If I understand, because of the automatic "not compile and hot > deploy" of CF templates under CFMX -- > You can incorporate CF changes, without recycling the system. > > On a pure Java/JSP system, you would likely need to recycle the system. > > Appears to be an advantage for CFMX. > > Is there some endemic reason that Java programs can't be/aren't "hot > deployed" similar to the way CFMX does it? > > This whole server side is a big unknown to me -- thanks for your > answers, and your patience! > > This is good poop! > > Dick > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
