I've tried following the instructions for multiple workers but I can't make sense of the behaviour I'm seeing.
I have a Rails app which calls out to an API, this API in turn makes an http request back to the original Rails app. If I run my Rails app with Unicorn and multiple workers this works as expected. If I run the Rails app using pow and try the same thing the request back into the Rails app appears to be blocked (waiting for a worker/process?).
As an experiment I tried a long running request to the same rails app, via pow. Then start a second request. By tailing the logs I can see Rails responding but again the browser seems to hang waiting for something until the original request is complete.
Any explanation of this behaviour or help in allowing me to run the scenario correctly using pow would be appreciated, thanks.
I've tried following the instructions for multiple workers but I can't make sense of the behaviour I'm seeing.
I have a Rails app which calls out to an API, this API in turn makes an http request back to the original Rails app. If I run my Rails app with Unicorn and multiple workers this works as expected. If I run the Rails app using pow and try the same thing the request back into the Rails app appears to be blocked (waiting for a worker/process?).
As an experiment I tried a long running request to the same rails app, via pow. Then start a second request. By tailing the logs I can see Rails responding but again the browser seems to hang waiting for something until the original request is complete.
Any explanation of this behaviour or help in allowing me to run the scenario correctly using pow would be appreciated, thanks.