Redisent does not handle errors when the socket connection has been interrupted for whatever reason

[chrisboulton]

Redisent does not handle errors when the socket connection has been interrupted for whatever reason

[d11wtq]

Yeah, this is easy to replicate. I see you already used an approach given by somebody in a php.net comment thread, with regards to checking the number of bytes written by fwrite() against the length of the string given. Since this doesn't seem to work, I'm going to investigate a solution that registers a SIGPIPE handler, which is designed for this purpose and seems more foolproof.

http://en.wikipedia.org/wiki/SIGPIPE

To set this up, simply create a fake job that sleeps for 10-20 seconds, and while it's sleeping, shut down redis from underneath it. The job will finish after it has slept, then its worker will then spin out of control as it tries to mark itself as done.

In addition to trapping SIGPIPE, moving the usleep() call outside of all conditions would certainly reduce the impact any potential error does have on the server.

[d11wtq]

Closing this as I have submitted a pull request with a fix.