T
Tim Kuehn
Guest
Mike Fechner “Upgrading systems running "old" appservers.” Not sure what you mean with „old“ AppServers. As opposed to the next-gen appserver PSC announced at Exchange. Mike Fechner You think trimming AppServer agents every now and then is a bad thing? If it’s static or not – if you load classes into the memory of the AppServer and don’t know which classes in memory are from which release of the server code base (some loaded before your on the fly update, some loaded after your on the fly update) that sounds like a nightmare came true. I'm going by what Mary told me - that upgrading appservers with static class code operational on them was a problem. I know that statics can also cause issues for sites that use "on-the-fly" upgrade scenarios as well. Mike Fechner On the other hand, the nature of the static utility classes may allow to update them less frequently than actual business logic. So once a year, I believe that trimming AppServer agents is o.k.. Others may actually be using the auto-trim feature of AppServer agents – without lacking any scalability. /If/ that's how they're used in the system. If someone uses statics for business logic, etc. then the story gets more complicated. Mike Fechner Aren’t we making too much assumptions already about what the poor OP is intending to do? Not really, this is just relating some potential issues to look out for. I'm a bit surprised Julian hasn't weighed in with his experiences yet....
Continue reading...
Continue reading...