Re: Problem contacting to 1085 and no instance available

It seems WO 5.2.3 addressed the close wait problem...........
http://docs.info.apple.com/article.html?artnum=107873

<snip>
wotaskd and monitor leave sockets in a CLOSE_WAIT state

  Apple Reference 3535483

  ISSUE:

  Under some circumstances, a socket leak occurred when http 1.0 was 
used. We think a majority of the CLOSE_WAIT problems pertaining to 
wotaskd and monitor are addressed.

  RESOLUTION:

  This issue has been resolved.

<snip>

To use WO 5.2.3, it seems you have to upgrade to OS X 10.3.3 or later, 
XCode 1.1 or later, and Java 1.4.2

-Kieran

On Jun 13, 2004, at 5:18 PM, Ute Hoffmann wrote:

> Hallo,
> I managed to force-quit a instance, which was no longer accessible. 
> From this moment Monitor gave no more errors "failed to contact 1085".
>
> I had a great number of close_waits in netstat before I force quitted 
> this instance, which disappeared afterwards.
>
> The close-waits were of the form
>
> tcp4       0      0  serverx.abc.51120 serverx.abc.globe CLOSE_WAIT
>
> Some of them had a process number attached, but the process did not 
> show in ps -ax.
>
> All of the close_waits had different port numbers in the 5000 range.
>
> They all connected to .globe. Does someone know what .globe means? Do 
> those close-waits shed any light on why this instance was no longer 
> accessible? The number of close waits of this typ increased with time 
> slowly.
>
> System: Mac Os X 10.2.8 Client and corresponding WO.
>
> Thanks for some hints,
>
> Regards,
> Ute
>
> _________________________________________________________________
> STOP MORE SPAM with the new MSN 8 and get 2 months FREE* 
> http://join.msn.com/?page=features/junkmail
>
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>
>

___________________________________
Kieran Kelleher
SmartleadsUSA,LLC
2656 West Lake Rd
Palm Harbor, FL 34684
[email protected]
727-785-0766 x33