Okay, good to know. Kill is definitely the desired action. I guess that makes my next question: Does anyone have bash scripts or something similar that hit a direct action on all instances of a woapp and take action if they are non-responsive which can be shared?
On Aug 14, 2014, at 11:16 AM, Chuck Hill <ch...@global-village.net> wrote: > It depends on how hung it is. If you scroll down to the bottom of the config > page for an instance, there is a Force Quit button. But that relies on the > app being responsive to admin requests. If there are no worker threads > available, it won’t work. And and I don’t think it can kill the app if there > is an actual deadlock or live lock, e.g it is not a kill -KILL > > Chuck > > > On 2014-08-14, 11:13 AM, "Ramsey Gurley" wrote: > > Is there a built in way through java monitor to kill any instance that > becomes non-responsive automatically? I’d rather not reinvent the wheel if > something like this exists already. > > Also, is there any good documentation on enabling JMX monitoring of woapps? > In combination with a monitoring tool like Nagios or some other monitoring > solution? > > Thanks, > > Ramsey > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/chill%40global-village.net > > This email sent to ch...@global-village.net
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
