[EMAIL PROTECTED] wrote: > Steve, > > On 2/4/07, Steve Brewin <[EMAIL PROTECTED]> wrote: > > > With these two issues resolved a simple script could be > used to bring up the > > new server with a new and already tested configuration, > switch the IP > > redirection to point to this server, then "drain and close" > the old server. > > If you could "drain and close" the spool manager without bringing down > the other components you would pause processing and allow yourself the > easier option of simply instantiating a whole new configuration but > also provide the appearance of not stopping, because you'd never go > off-line. The trick would be to deal with statics & singletons > correctly by dumping the whole spoolmanager classloader tree. > It might also make sense to divide up the config of James into > distinct component configurations. > > d. Yes, I thought about this and other tricks. Switching to another instance is much less tricky. In my simpleton scenario, all that is required of "drain and close" is to ensure that everything in the pipeline is processed before shutting down the server. There is no need to worry about statics & singletons and so worth, the JVM is killed. The "appearance of not stopping" is achieved simply by routing to the new server instance.
It's neither smart or elegant, but it achieves the goal in a lightweight manner. Cheers Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
