I realise this isn't very well-behaved, but any others will probably be
dealing with the same problems. At this point in time there is only one
web application.
Perhaps there is another solution - eg send an email on failure and get
an administrator to check in on the problem.
Cheers,
Brett
E B wrote:
>Do you mean a webapp should be able to stop the
>appserver tomcat ?
>If this is what you wanted, then will other webapps be
>
>happy with this ?
>
>
>
> --- Brett Porter <[EMAIL PROTECTED]> wrote: >
>Hi,
>
>>I saw a message a while back on this, but don't
>>remember a solution and
>>failed to find it in the archives.
>>
>>I am looking to shutdown Tomcat 4 if a set of
>>initialisation functions
>>fail. These functions are in the init() method of a
>>servlet that is set
>>to load on startup (the first).
>>
>>Throwing a ServletException doesn't stop Tomcat, and
>>I tried calling
>>Bootstrap.main( new String[] { "stop" } ); but that
>>didn't unbind it
>>from the port either (it didn't give me any log
>>messages either, but it
>>did prevent anything executing after that :)
>>
>>Thanks,
>>Brett Porter
>>
>>
>>
>
>____________________________________________________________
>Nokia Game is on again.
>Go to http://uk.yahoo.com/nokiagame/ and join the new
>all media adventure before November 3rd.
>
