Re: "Too many open files" and reboot fail advice

Chuck,

I see, I suspected 5.2.3 fixed it. There are two reasons why I believe 
5.2.3 is broken for JC. The first is that two big JC users on the wodev 
list found the EODistribution layer to always break down after some use 
with 5.2.3. One was Nick Pilch and another Benjamin J Doherty.

Secondly, I couldn't get my JC app to work reliably myself via a web server 
and WO5.2.3, though I must admit it seemed to work ok via direct connect. 
Even more strangely it worked via internet connections from some ISPs but 
not others. The stack trace I got on the client was as below and I have no 
solution:

java.lang.IllegalStateException: Reentered responseToMessage()
         atom.webobjects.eodistribution.client.EOHTTPChannel.responseToMessage(EOHTTPChannel.java:591)
         at  mp.client.MPHTTPChannel.responseToMessage(MPHTTPChannel.java:301)
         at 
com.webobjects.eodistribution.client.EODistributedObjectStore._send(EODistributedObjectStore.java:590)
         at 
com.webobjects.eodistribution.client.EODistributedObjectStore._send(EODistributedObjectStore.java:619)
         at 
com.webobjects.eodistribution.client.EODistributedObjectStore.invokeRemoteMethodWithKeyPath(EODistributedObjectStore.java:1041)
         at mp.client.Utils.invokeServerMethod(Utils.java:1898)

This doesn't happen with WO5.2.2.
John

At 18:10 22/02/2005, Chuck Hill wrote:

> From the 5.2.3 Release Notes 
> http://docs.info.apple.com/article.html?artnum=107873
>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.
>
>I'm pretty sure that it was the 5.2.3 release that fixed this for us.
>
>I'm also interested in what you think is broken in WO 5.2.3 for 
>JavaClient.  I know someone using Java Client and WO 5.2.3 and am not 
>aware of them having any issues to it (well, other than documentation and 
>completeness of implementation :-).
>
>Chuck
>
>
>On Feb 22, 2005, at 7:47 AM, John Pollard wrote:
>
>>I have been monitoring the number of connections that wotaskd holds open 
>>and formed a link to JavaMonitor. Provided I am not using JavaMonitor, 
>>the number of connections holds steady. When using JavaMonitor, the 
>>connections increases upwards until the file descriptor limit is met. 
>>Whether avoiding using JavaMonitor will cure all my "Too many files open" 
>>problems remains to be seen. I thought I'd mention this observation as I 
>>have not seen it elsewhere. Although this is old news for most WO users, 
>>JC WO users stuck on WO5.2.2 may be interested.
>>
>>At 10:54 21/02/2005, John Pollard wrote:
>>
>>>All,
>>>
>>>We are currently suffering the dreaded "Too many open files" problem 
>>>that I have now read about in many previous postings to this list. It 
>>>has happened since I moved to Panther.
>>>
>>>JavaMonitor fails to stop/start instances, the instances themselves fill 
>>>their log files with IOExceptions, too many open files.
>>>...
>>
>>_______________________________________________
>>WebObjects-admin mailing list
>>[email protected]
>>http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>--
>Practical WebObjects - a book for intermediate WebObjects developers who 
>want to increase their overall knowledge of WebObjects, or those who are 
>trying to solve specific application development problems.
>http://www.global-village.net/products/practical_webobjects
>
>
>
>
>
>
>
>-- incoming mail is certified Virus Free.
>Checked by AVG Anti-Virus.
>Version: 7.0.300 / Virus Database: 265 - Release Date: 14/02/2005

John Pollard
020 889 22143
077 422 10024