Re: clarification on "Correct error in fix for 49683"

2012-02-10 Thread Pid
On 09/02/2012 23:42, Janne Jalkanen wrote: > > Just to confirm - 7.0.25 seems to solve the problem for the most part. "Most part"? So there is still a leak? p > /Janne > > On 24 Jan 2012, at 10:53, Janne Jalkanen wrote: > >> >> Been running 7.0.25 in production now for a day and the fd leak

Re: clarification on "Correct error in fix for 49683"

2012-02-09 Thread Janne Jalkanen
Just to confirm - 7.0.25 seems to solve the problem for the most part. /Janne On 24 Jan 2012, at 10:53, Janne Jalkanen wrote: > > Been running 7.0.25 in production now for a day and the fd leak seems at > least mitigated somewhat. lsof still lists a few open sockets left by > Tomcat, but th

Re: clarification on "Correct error in fix for 49683"

2012-01-24 Thread Janne Jalkanen
Been running 7.0.25 in production now for a day and the fd leak seems at least mitigated somewhat. lsof still lists a few open sockets left by Tomcat, but this is less than what 7.0.23/.22 was doing. I will continue to run this a bit further and report back in a day or two whether the situatio

clarification on "Correct error in fix for 49683"

2012-01-21 Thread Mike Wertheim
The change log for Tomcat 7.0.25 contains this entry: "Correct error in fix for 49683. (markt)" Is this bug fix expected to fix the file descriptor leak that was reported in Tomcat 7.0.23? - To unsubscribe, e-mail: users-unsubscr