Date: Wed, 23 Aug 2000 11:06:31 +0930 (CST) From: Greg Lewis <glewis@ares.trc.adelaide.edu.au> To: Joe Shevland <shevlandj@kpi.com.au> Cc: "List, FreeBSD Java" <freebsd-java@FreeBSD.ORG> Subject: Re: Possible resource leak: JDK1.2.2/Tomcat 3.1 Message-ID: <200008230136.LAA07615@ares.trc.adelaide.edu.au> In-Reply-To: <IOEALGALKLLJILALBBOMKEKDCBAA.shevlandj@kpi.com.au> from Joe Shevland at "Aug 22, 2000 01:00:09 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Joe Shevland wrote: > I've been running the JDK1.2.2 port (patchset 10) and Tomcat 3.1 on FreeBSD 3.5 (stable-20000718) for the last ~17 days (that was the uptime of the machine before the crash I'll describe). Yesterday I attempted to SSH to the box to do something and it booted me straight off. Toddling up to the dingy computer room, I see on the console that it has run of out file descriptors to allocate. I've never seen this before with FreeBSD, and it had the effect I couldn't log on or do anything (apart from, I know I'm a sinner, the three-figure salute). > > Are there any log files I should be aware of that may indicate the cause of the runaway file descriptors? I'm blindly pointing the finger at JDK/Tomcat because it must perform a lot of file IO (the box also runs sendmail (light load for the configration of the box) and sshd but thats about it). Can you periodically maybe check what files are open (I think a utility like lsof will do this for you)? That way we can hopefully tell if things are being kept open that shouldn't. -- Greg Lewis glewis@trc.adelaide.edu.au Computing Officer +61 8 8303 5083 Teletraffic Research Centre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008230136.LAA07615>