D
dbeavon
Guest
I'm now using the approach where I change minSrvrInstance to zero and autoTrimTimeout to 10 seconds so that after a ten second period of inactivity, the appserver agents will be trimmed, thereby picking up new r-code when the agents are restarted. This seems to work pretty well. As expected, the approach does add an extra second or so whenever my .Net application re-launches and connects for the first time (after the 10-sec-app-server-auto-trim). Despite the extra second delay, I think I still like this approach (better than the "flush hack" which is really only a good solution for a single ABL session). ... And one day if I don't want my agents auto-trimming at all (eg. when my *entire* day is going to be spent on the VS.Net side of things), then I'll just create a keep-alive utility that sends some bogus requests to those appserver agents every five seconds in order to make sure they are always "warm" and ready for round-trips.
Continue reading...
Continue reading...