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 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 situation 
> is getting worse.
> 
> java     4086 ubuntu   10u     sock                0,6       0t0  73725644 
> can't identify protocol
> java     4086 ubuntu   59u     sock                0,6       0t0  77721715 
> can't identify protocol
> java     4086 ubuntu   96u     sock                0,6       0t0  77721057 
> can't identify protocol
> java     4086 ubuntu  108u     sock                0,6       0t0  77723538 
> can't identify protocol
> java     4086 ubuntu  119u     sock                0,6       0t0  77722327 
> can't identify protocol
> java     4086 ubuntu  132u     sock                0,6       0t0  77724248 
> can't identify protocol
> java     4086 ubuntu  134u     sock                0,6       0t0  77723129 
> can't identify protocol
> 
> 
> /Janne
> 
> On 21 Jan 2012, at 23:19, Mike Wertheim wrote:
> 
>> 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...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org


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

Reply via email to