Re: CLOSE_WAIT issues

Sacha,

As you say is disturbing to hear people report CLOSE_WAITs with 5.3 also.
I have your point about an OS install in mind, thanks for the tip.
At present I am rebooting every night and since doing so, no hiccups yet, 
though I do not count this as a long term solution.
wotaskd was definitely restarting.
Though we were restarting wotaskd previously (SystemRestarter seems to work 
ok), we were killing/restarting the stuck applications. Perhaps scheduling 
restarts for every app instance and restarting wotaskd every night is 
normal practice and what we should have been doing?

>I suppose it is possible that there is some difference between the 2
>versions, but I don't think so.  I don't recommend what you're doing
>(simply because spending even a few hours configuring a client box is
>usually not worth it if you can buy something that will work out-of- 
>the-box), but I would expect to see missing classes or something
>along those lines if that was your problem.

I think we were almost forced to keep away from X Server because it came 
preinstalled with a version of WO that at the time completely broke our 
Java Client applications and there was no supported way of having an older 
WO version. I actually find that the installation work needed on X Client 
is pretty much the same as on X Server.


>Have you verified that the CLOSE_WAIT does, in fact, occur when
>communicating to your DB?  Or is it between wotaskd and the apps.  My
>experience is with the latter...

I have been looking into this a bit more. We do have CLOSE_WAITs from some 
of our WO apps connecting to mysql, but I haven't seen these grow out of 
control (have only seen one per app instance) in the way they do for the 
wotaskd CLOSE_WAIT connections. I expect there is something slightly wrong 
there, but I don't have any evidence that this stops anything working. 
Themain problem seems to be when the CLOSE_WAITs happen between wotaskd and 
app instances as you say and the app instances become non responsive.

I am yet to see a repeat (since adding nightly reboots) so have not yet had 
a chance to get a stack trace.

John