On Thu, 31 Jan 2002 11:48, Jar Lyons wrote: > :I just changed my application to do a System.exit(..) if a > > BindException is thrown during initialization > > What I wanted to do was throw a RuntimeException .... or anything that > would reliably bring the system down. > > But alas ... it looks like everything upstream gets swallowed .... > > This means that if you inadvertently start a server twice .... the > second one will fail on the bind (for obvious reasons) > and then stay running. > > Any suggestions other than System.exit?
You should now be able to throw an exception during the apps startup either from a block or a block listener and the application will be killed. If there are now applications left in the kernel then it should go down. Well at least I think so ... will test it in a bit :) BTW This should probably goto the [EMAIL PROTECTED] list -- Cheers, Pete *---------------------------------------------------------* | Contrary to popular belief, UNIX is user-friendly. It | | just happens to be selective on who it makes friendship | | with. | | - Richard Cook | *---------------------------------------------------------* -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
