On Jul 13, 2010, at 17:31 , Scott Ferguson wrote:

> Scott Ferguson wrote:
>> Rob Lockstone wrote:
>>> Looking at the code for ResinActor/ResinLink/HmtpLink, the run() 
>>> method in HmtpLink could exit on an IOException and not log any 
>>> details about the cause, and that would cause Resin to exit without 
>>> being explicitly told to, no?
>> The exception would be logged by the thread pool code at the warning 
>> level, but I've added a catch/log to the ResinLink to make that clearer.
>> An IO exception on that socket would cause Resin to exit.
> To clarify, though, in that situation, the watchdog would restart Resin.

That's exactly what I would have expected. But it didn't happen. It was offline 
for well over an hour before I manually restarted it.


resin-interest mailing list

Reply via email to