I'm trying to kick off simple (yet long running) background processes from within my rails app. I'm using Tom Anderson's spawn plugin http://rubyforge.org/projects/spawn/ to fork a child process and unhook the active record DB connections to keep rails happy. Anyway, everything works great when I hit a mongrel process directly (http://myapp:3000/controller/action). The action quickly executes, the results are returned to my browser, and the child process takes its time doing the heavy lifting. I can hit that mongrel process again and verify that it's free to serve up another request.
Life is good-- that is until, I bring nginx into the mix. With nginx proxying to the upstream :3000 mongrel, the response isn't immediately returned to my browser. Instead, the rails log file shows that the request is finished, but my browser continues to spin, waiting for the response. If I stop the request, I can load an alternate action to verify that the lone mongrel is free to serve another request. Has anyone had success with nginx, mongrel, and child processes? I just installed pen to balance the single mongrel, and it worked as expected. My dev box is intel mac, ruby 1.8.6, mongrel 1.1.2, nginx 0.5.34 (tried with same results on 0.5.32) Thanks! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
