Anybody have a procedure to do a "rolling restart" of web service connection pools? For example, I made a change to a sub program that backs a web service, but I've found that restarting the pools is the best way to ensure the new changes are served. I've had it for example where 3 out of 4 calls get the new logic, but that fourth one will still be running the old code, and it doesn't seem to refresh itself.

So I'd like to be able to kill one of the channels at a time, and restart them in rolling fashion so I can make these production pushes without affecting availability. I had thought about looking up process IDs and killing them on the server for instance. Anybody know of a way to do this? If not maybe I'll make it an improvement suggestion