0700
> To:
> Subject: Re: Thread Blocking Radomly
>
> I originally thought it was replication but one of the servers
> exhibited the same issue with polling disabled. If it is tomcat why
> would it block for so long on a simple log rotation?
>
> Additionally, we see similar t
Mark Miller wrote:
> Its certainly happening when its trying to switch to a new log file. It
> doesn't try and close the file otherwise. Why there is such a pause
> doing it, I dunno. Perhaps because there are tons of file descriptors
> around?
>
> Does it happen on a fresh system, or did it just s
Its certainly happening when its trying to switch to a new log file. It
doesn't try and close the file otherwise. Why there is such a pause
doing it, I dunno. Perhaps because there are tons of file descriptors
around?
Does it happen on a fresh system, or did it just start after running for
a long
I originally thought it was replication but one of the servers
exhibited the same issue with polling disabled. If it is tomcat why
would it block for so long on a simple log rotation?
Additionally, we see similar things during the day. Replication often
is around the occurance but never at
Perhaps something like Tomcat rotating it's log files nightly?
-Yonik
http://www.lucidimagination.com
On Sun, Sep 27, 2009 at 11:13 AM, Mark Miller wrote:
> Doesn't sound so random ;)
>
> Do you have anything specific going on at that time? Replication,
> something else scheduled? Pretty odd it
Doesn't sound so random ;)
Do you have anything specific going on at that time? Replication,
something else scheduled? Pretty odd it would happen at around the same
time every night unless something is set to occur then ...
Jeff Newburn wrote:
> It appears that a few seconds after midnight every
