ThreadsOnFork worker never seems to actually connect on Windows

nesquena / backburner

Simple and reliable beanstalkd job queue for ruby

http://nesquena.github.com/backburner

MIT License

428 stars 68 forks source link

ThreadsOnFork worker never seems to actually connect on Windows #105

Closed contentfree closed 9 years ago

contentfree commented 9 years ago

Yes I know: Windows… However, it's a requirement for me for a particular job task.

Running the backburner CLI seems to start the process correctly, but no connection to beanstalkd is made (and no work is done). Killing the process does not print out the expected [ThreadsOnFork workers] Stopping forks:

Anyone know of a fix?

nesquena commented 9 years ago

ThreadsOnFork was never implemented to work on Windows unfortunately if I recall correctly it only works on unix-based systems. We should probably do a better job of documenting this and/or exploring if there's a fix.