Re: Failed to contact xxxx-1085, ellpack

Chuck,

I'm not ambitious by nature, but I had a go by editing the 
wotaskd.woa/wotaskd script and adding to the last eval 
line >/var/log/wotaskd.log 2>&1

Interestingly, when I told WO to restart its services, this log file jumped 
into life with lots of exceptions saying that the port was already in use.

So I rebooted and things started up ok with some minor output in wotaskd.log.

However, sending kill -QUIT to the wotaskd process didn't produce a stack 
trace in this file. I wonder what I am getting wrong here.

John

At 18:50 03/10/2005, Chuck Hill wrote:

>This looks to be a message from wotaskd, probably when returning the
>configuration information to JavaMonitor.  It looks like something is
>occupying wotaskd so that it is responding too slowly to requests.
>The next time this happens, get some threaddumps from wotaskd (check
>beforehand to ensure that it is not configured to send this to /dev/ null, 
>I suspect that is the default).  Take them several seconds / a
>minute apart and see if that shows anything.  Or you could get really
>ambitious and run wotaskd in a Java debugger and attach to it when
>this happens and see where the holdup is.
>
>And while we are grasping at straws, add "- D_DeploymentDebugging=true" 
>when starting wotaskd or JavaMonitor
>makes the tools very talkative.  They may say something interesting.
>
>
>Chuck