tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Funk <>
Subject Re: Reaching ulimit values for open files can generate huge log files
Date Mon, 21 Feb 2011 17:33:40 GMT
Do you want to limit the try/catch scope to just 
serverSocketFactory.acceptSocket since setSocketOptions() can also throw 

Is there a case where a client can induce an exception while 
setSocketOptions() is processing?


On 2/21/2011 10:21 AM, Mark Thomas wrote:
> The ASF Sonar installation managed to generate 46GB of identical log
> messages [1] today in the 8 hours it took to notice it was down.
> While better monitoring would/should have identified the problem sooner,
> it does demonstrate a problem with the acceptor threads in all three
> endpoints. If there is a system-level issue that causes the accept()
> call to always fail (such as hitting the ulimit) then the endpoint
> essentially enters a loop where it logs an error message for every
> iteration of the loop. This will result in many log messages per second.
> I'd like to do something about this. I was thinking of something along
> the lines of the following for each endpoint.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message