I checked the code that write the "Watchdog default Worker ### has time
to sleep -###" and it seems unchanged since 2002.
The code explicitly handle times less than 0 milliseconds, so it should
not be a problem.
This probably only happens because your server is on 100% cpu and the
watchdog thread is mostly late. The watchdog code is to handle the
connection timeouts and when it writes a negative value it simply
suddenly run the "watchdog target" (idleClose).
The log snippet confirm that the "SMTP Connection has idled out".
Stefano
Nathan Cheng wrote:
[...]
--------------------------------
25/04/06 12:37:38 DEBUG smtpserver: Watchdog default Worker #30 has time
to sleep 300000
...
25/04/06 12:42:38 DEBUG smtpserver: Watchdog default Worker #30 has time
to sleep -75
25/04/06 12:42:38 ERROR smtpserver: SMTP Connection has idled out.
25/04/06 12:42:38 DEBUG smtpserver: Watchdog default Worker #30 is
exiting run().
--------------------------------
From this point it's about 30 minutes of hang time before we'll get a
whole string of errors in the smtp log, and then James'll start back up
again.
What does it mean to sleep -71 milliseconds?
Nathan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
