Re: too many open files

Hey Folks,

Remember this discussion that we had a fortnight ago? I was telling you 
my story: a second team deployed few WO apps on the same 10.2.8/WO 
5.2.1 Xserve, and suddenly all these problems described below start 
popping up. Most of you were finger-pointing  at wotaskd or JavaMonitor 
... there were even thoughts that this happens if other monitors are 
running on the same network etc.

My "feeling" was (based on past - bad - experience) that it is our 
(developer's) mistake related to WOResourceManager  usage. It turned 
out to be almost correct - at least in our case.

The problem was fixed by setting unused file handles to null and 
calling System.gc(). That's all! No EC (dead)locks, no Monitor 
mysteries...

I was always claiming that I would prefer the Objective-C way of memory 
management, and this is yet another reason why I feel I am right :-)

cheers

-- georg --

"War is God's way of teaching Americans about geography."
Ambrose Bierce, writer (1842-1914)

On Jan 29, 2004, at 2:53 PM, Simon wrote:

>
> we've seen this problem when running multiple apps on a panther server 
> and re-boot is the only way out we have found. another panther-related 
> problem we see randomly is this:
>
> Cannot write to file /Library/WebObjects/Configuration/SiteConfig.xml. 
> Possible Permissions Problem.
>
> ... when trying to shut down an instance. however, if we keep clicking 
> the "shut down all instances" button then it does eventually go away 
> and the instances do shut down.
>
> simon
>
>
> On 28 Jan 2004, at 21:39, Pierre Frisch wrote:
>
>> David,
>>
>> I would disagree with you on this one. I agree that on WO this can be 
>> home grown however in this case there is a problem in Panther. I know 
>> because I have had a machine with a bunch of application running on 
>> Jaguar that was very stable. The only thing that has changed is the 
>> OS and the version of WO and now I have all sorts of troubles.
>>
>> There are two problems on 10.2.3 one with Apache and one with 
>> wotaskd. The Apache one is fairly old: the adaptor does not close the 
>> connections to the app immediately and let them linger with consume 
>> some of those open file. In addition wotaskd appears to have 
>> developed a similar disease on Panther. The combination of both is 
>> lethal. You can reduce the wotskd problem by disabling the 1085 
>> config distribution feature and use teh file config.
>>
>> Pierre
>> --
>> Pierre Frisch
>> sPearWay Ltd.
>> sPearCat Web Catalogs, the flexibility of custom design, the price of 
>> a package.
>> http://www.spearcat.com/
>>
>> On Jan 28, 2004, at 12:46, David Teran wrote:
>>
>>> Hi,
>>>
>>> On 28.01.2004, at 21:39, Jürgen Rohrbach wrote:
>>>
>>>> hello,
>>>>
>>>> i have read all the postings with "too many open files" but i have 
>>>> still a problem to find the correct solution/workaround.
>>>> after 2-3 days my app has the following in the log file:
>>>>
>>>> IOException: too many open files
>>>>
>>>>
>>>> which solutions work to get rid of this shit!
>>>>
>>>
>>>
>>> best is to check your code. It turns out that the 'shit' is 
>>> homegrown.
>>>
>>> Things to check:
>>>
>>> 1) wrong usage of Process instances
>>> 2) open streams
>>> 3) unhandled exceptions
>>> 4) wrong deployment
>>> ...
>>>
>>> This might annoying for you but the problem is in your code. Do you 
>>> know the lsof command or are you working on windows?
>>>
>>> cheers David
>>>
>>> _______________________________________________
>>> WebObjects-admin mailing list
>>> [email protected]
>>> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>>>
>> _______________________________________________
>> WebObjects-admin mailing list
>> [email protected]
>> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
> _______________________________________________
> WebObjects-admin mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-admin
>


Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196