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

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.
>...