"Remy Maucherat" <[EMAIL PROTECTED]> wrote:
>> Ok... I'm facing this little problem... I have a servlet creating a RMI
>> registry, and that binds to a port, creates a non-daemon Thread...
>> Yadayadayada... You know where I want to end up to...
>>
>> Now, catalina.sh stop doesn't work anymore, because I found no apparent way
>> of shutting down that RMI registry...
>>
>> Do some of you know HOW to shut down a RMI registry?
>
> Sorry, I don't.
Crap...
>> Otherwise I'd propose
>> to revert back to org.apache.catalina.startup.Catalina version 1.44.
>
> -1. No, because it's equivalent to not attempting to shutdown cleanly.
We can control the threads invoking destroy() in the different contexts, and
when they all exit, well, we exit...
If a servlet creates a thread, and during its destruction doesn't
synchronize its own thread reentrance (doesn't wait for it to die before
returning from destroy()), then it's a servlet problem, but we won't hold a
process on the server forever.
> If you want to do that, write a servlet with System.exit() in its destroy
> method, it would be the same. Or you can kill the process.
Yeah, so that when my context gets reloaded because of a change the whole
f***ing servlet engine falls over :) RAD! :)
Pier
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
