----- Original Message ----- From: "Peter Donald" <[EMAIL PROTECTED]>
> In the init process you can just throw an exception from one of the lifecycle > methods. This will cause James to attempt to shut down gracefully. > > During runtime there is not a current way that is exposed to > ServerApplications however there will be in the future. In the meantime you > should be able to call System.exit() and it will gracefully detect this and > attempt a shutdown (I think). However make sure you never expect any code > after exit() to be executed or synchronization locks to be honoured. Ok, thanks. I'll have to see what's going wrong in James's init, but I notice that frequently if you make a mistake in the conf file, James/Avalon will just repeatedly attempt to load the configuration until you get an OutOfMemoryError. I'll try to get some better information to diagnose the problem though. Serge Knystautas Loki Technologies - Unstoppable Websites http://www.lokitech.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
