Next time it happens I will do some forensics before I restart Tomcat. Things such as a JVM full thread stack dump, netstat, fstat, etc.
Then I may have a better idea where the file descriptor leak is. One thing I have found is that the way GC works may impact the number of file descriptors. If you don't explicitly close some IO streams the file descriptor associated with that stream will still exist until the object is finalized during garbage collection. Regards, Glenn Nielsen On Sun, Dec 18, 2005 at 08:59:22AM -0800, Allen Gilliland wrote: > Actually, you may also want to check the search stuff. i have seen that > same thing happen with Lucene in other apps before. > > -- Allen > > > On Sun, 2005-12-18 at 06:38, Anil Gangolli wrote: > > Sounds like something we need to track and look into. Please file a bug > > report on our issue tracker: > > http://opensource2.atlassian.com/projects/roller/secure/Dashboard.jspa > > > > --a. > > > > Glenn Nielsen wrote: > > > > >Since upgrading to roller 1.2 and configuring several feeds in > > >the Planet Tomcat has failed twice due to running out of file > > >descriptors. Both times the failure occurred about 10 days > > >after Tomcat was started. I suspect the background threads > > >for the Planet may be leaking file descriptors for sockets > > >but haven't confirmed this yet. > > > > > >FreeBSD 5.3, Java 1.4, Tomcat 4.1, Roller 1.2. > > > > > >Has anyone had similar problems? > > > > > >Regards, > > > > > >Glenn Nielsen
