Re: Graceful shutdown of WO apps + monitor + wotaskd
Re: Graceful shutdown of WO apps + monitor + wotaskd
- Subject: Re: Graceful shutdown of WO apps + monitor + wotaskd
- From: Kieran Kelleher <email@hidden>
- Date: Tue, 5 May 2009 10:32:38 -0400
Depends on how wotaskd and womonitor are configured to run.
Assuming you are using Leopard, and using launchd jobs, you can
restart them by telling launchctl to stop the job ... and they should
automatically restart....
for example
sudo launchctl stop com.webobjects.wotaskd
sudo launchctl stop com.webobjects.womonitor
(assuming "com.webobjects.wotaskd" is the name of the launchd task)
usually killing wotaskd results in the managed instances getting
killed too IIRC.
you can also kill an instance by getting its pid and using kill.
To get a pid of an instance, you get its port number in womonitor and do
sudo lsof -i tcp:<port-num>
if your apps are actually misbehaving, refusing connections, and
basically hung or deadlocked, then it is useful to jstack them before
killing them to see what is wrong:
sudo jstack <pid>
HTH, Kieran
On May 5, 2009, at 10:24 AM, Greg Brown wrote:
Hi,
There isn't much I could find about programatically shutting down
the webobjects system, so I assume something like a
SIGTERM signal
would, if sent to all three, terminate all webobjects programs on
unix.
Is there a nicer way? I assume a reboot does pretty much the same
thing.
Thanks!
Greg
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden