What to Do When Wotaskd Dies
What to Do When Wotaskd Dies
- Subject: What to Do When Wotaskd Dies
- From: Yisrael Ari Espinoza <email@hidden>
- Date: Thu, 29 Jul 2004 10:34:20 -0700
I'm having a difficult time trying to understand why Java Monitor never
seems to do the things we want it to, BUT, having said that, I've got a
fresh new Xserve with 4 GB of memory, 10 instances configured with
generous memory for each (I use a lot of direct actions) and every 10
hours or so, my apps stop responding.
What does one do when wotaskd dies? I also see this in the
/var/log/webobjects.log file:
. `wotaskd' terminated with an error (`143'). Scaling wait time ...
. Execution not counted as a success.
bootstrap_look_up() failed (ipc/send) invalid destination port
javawoservice.sh: `wotaskd' will restart in 5 seconds ...
bootstrap_look_up() failed (ipc/send) invalid destination port
bootstrap_look_up() failed (ipc/send) invalid destination port
What is error 143?
Yisrael
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.