Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of Janne.Jalkanen@ecyrd.com
 designates 87.108.86.67 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: File leak in 7.0.23?
From: Janne Jalkanen <Janne.Jalkanen@ecyrd.com>
In-Reply-To: <4EFF124E.3070509@pidster.com>
Date: Sat, 31 Dec 2011 16:22:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DF97F54-4851-4819-BAD5-A5FFBC21F91C@ecyrd.com>
References: <88564FD0-5E9B-47EC-B2C9-39ED4CB8A081@ecyrd.com>
 <4EFF0D2D.7070107@pidster.com>
 <9DEDD91D-755B-4290-A0A2-82CC8C50F07D@ecyrd.com>
 <4EFF124E.3070509@pidster.com>
To: "Tomcat Users List" <users@tomcat.apache.org>

> When did the problem start occurring and what else has changed?

Exactly at the time when I upgraded to 7.0.23.  I don't recall making =
any other modifications (I would've suspected them first ;-)

I will try to downgrade to 7.0.22 and lower to try and see if there's a =
difference between Tomcat versions.

> Can you stop monitoring with Munin and see if the problem goes away?
> If it does, I would consider that Munin may not be properly closing =
the
> connections it makes.

I did, and the problem did not go away. Open file count still =
increasing.

/Janne


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org