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

Pierre & Matthew,

Actually I already have these two processes running as root due to another 
issue and this didn't save me. However, if you are right about root 
processes having unlimited (or a higher limit of) open file descriptors, 
then that could explain why none of my processes could open files when the 
problem hit i.e. perhaps I had hit the machine limit.

So far I have shown that the number of open file descriptors held by 
wotaskd is perfectly stable and very low, provided I keep away from 
JavaMonitor. When I use JavaMonitor it starts ratcheting up and doesn't 
look like stopping. I now run /sbin/SystemStarter 'WebObjects Services' in 
the middle of the night to reset any damage JavaMonitor may have caused the 
previous day. For now my golden rule is not to leave JavaMonitor open and 
running, until I can move to WO5.2.3.

Interestingly when I ran an experiment on Mac OS X Client 10.3.7 / WO5.2.2 
I was also able to force up the wotaskd open file descriptors using 
JavaMonitor; but when it went somewhere over 1000 (not sure exactly), 
wotaskd appeared to automatically restart (it wasn't me). I can't really 
explain that, perhaps Mac OS X Client behaves differently to Mac OS X 
Server in this respect.

John

At 22:48 22/02/2005, Pierre Frisch wrote:

>Hi John,
>
>Actually it does. Root tasks have no limit as to the number of file 
>descriptor they can own. All other processes have a maximum number of file 
>descriptor. The problem is that Java and WO open quite a few descriptor 
>and you can quite quickly run out.
>
>This why running WO apps as root work better.
>
>Pierre
>--
>Pierre Frisch
>President
>sPearWay Ltd.
>phone: +1 604 929 9610 ext 6011
>email: [email protected]
>sPearCat Web Catalogs,
>Custom designed in-house
>with the click of a mouse.
>http://www.spearcat.com/