Comments on: Crash, Boom: Too Many Open Files… http://stuffthathappens.com/blog/2007/11/28/crash-boom-too-many-open-files/ Technology and Geek Stuff by Eric Burke Sat, 27 Feb 2010 14:52:46 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Martin.Smith http://stuffthathappens.com/blog/2007/11/28/crash-boom-too-many-open-files/comment-page-1/#comment-2178 Martin.Smith Thu, 29 Nov 2007 17:16:48 +0000 http://stuffthathappens.com/blog/2007/11/28/crash-boom-too-many-open-files/#comment-2178 simply using destroy() fixed the too many open files for me. How convenient this was posted the same day I ran into this error !! simply using destroy() fixed the too many open files for me.
How convenient this was posted the same day I ran into this error !!

]]> By: Sam.Halliday http://stuffthathappens.com/blog/2007/11/28/crash-boom-too-many-open-files/comment-page-1/#comment-2154 Sam.Halliday Thu, 29 Nov 2007 09:56:39 +0000 http://stuffthathappens.com/blog/2007/11/28/crash-boom-too-many-open-files/#comment-2154 What happens if the stdout really is System.out? Doesn't that close it? I've seen a bug where a Logger closes stderr and then nothing else can write to it in the entire application. What happens if the stdout really is System.out? Doesn’t that close it? I’ve seen a bug where a Logger closes stderr and then nothing else can write to it in the entire application.

]]> By: Jason Sankey http://stuffthathappens.com/blog/2007/11/28/crash-boom-too-many-open-files/comment-page-1/#comment-2137 Jason Sankey Thu, 29 Nov 2007 05:38:29 +0000 http://stuffthathappens.com/blog/2007/11/28/crash-boom-too-many-open-files/#comment-2137 Hey Eric, Ah yes, a familiar problem :). I agree the documentation is very poor here. The safest solution is as you suggest to close all streams yourself and call destroy. Looking into the JDK source, I see at least on Unix it will almost certainly close the streams itself in destroy() (it does them all in one try/catch which is a bit sloppy - what if the first close() fails?). More specifically, we also saw this problem with Pulse at a customer site using Subversion and OSX. I eventually tracked the problem to SvnKit and reported it with a patch: I believe the patch has been applied now in their svn repo. Hey Eric,

Ah yes, a familiar problem :) . I agree the documentation is very poor here. The safest solution is as you suggest to close all streams yourself and call destroy. Looking into the JDK source, I see at least on Unix it will almost certainly close the streams itself in destroy() (it does them all in one try/catch which is a bit sloppy – what if the first close() fails?).

More specifically, we also saw this problem with Pulse at a customer site using Subversion and OSX. I eventually tracked the problem to SvnKit and reported it with a patch: I believe the patch has been applied now in their svn repo.

]]>