4 messages in ru.sysoev.nginxRe: Rails Spawn plugin under nginx
FromSent OnAttachments
Tr SchneitMar 30, 2008 12:25 pm 
Corey DonohoeMar 30, 2008 12:43 pm 
Tr SchneitMar 30, 2008 1:38 pm 
Tom AndersonOct 13, 2008 2:59 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Rails Spawn plugin under nginxActions...
From:Tom Anderson (lis@ruby-forum.com)
Date:Oct 13, 2008 2:59:10 pm
List:ru.sysoev.nginx

BTW, the problems with Nginx were solved shortly after these messages appeared. The solution was to have spawn disconnect from the listening sockets in the child process. You should be able to use Spawn with nginx without problems now.

Tr Schneit wrote:

Howdy Corey- Thanks for your input. I will look into one of these alternatives.

Again, thanks for the quick response!

Corey Donohoe wrote:

Hey,

Every client we have using spawn at engine yard has problems. The short answer is just don't do it. You need to use real queueing a la bj, backgroundrb, starling, etc. I'm pretty sure that the upstream gets confused with all the fd closing/reopening/reconnecting.

__ Corey Donohoe cdon@engineyard.com (866) 518-9273 x207

-- Posted via http://www.ruby-forum.com/.