Forum: NGINX How can I run more than one process on Windows?

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
2974d09ac2541e892966b762aad84943?d=identicon&s=25 eComEvo (Guest)
on 2014-08-20 16:36
(Received via mailing list)
Despite sending an async request to the server over AJAX, the server
not respond until the previous unrelated request has finished. The
code is only broken in this way on Nginx, but runs perfectly on Apache.

This call will start a background process and it waits for it to
complete so
it can display the final result.

      type: 'GET',
      async: true,
      url: $(this).data('route'),
      data: $('input[name=data]').val(),
      dataType: 'json',
      success: function (data) { /* do stuff */}
      error: function (data) { /* handle errors */}

The below is called after the above, which on Apache requires 100ms to
execute and repeats itself, showing progress for data being written in

    checkStatusInterval = setInterval(function () {
        type: 'GET',
        async: false,
        cache: false,
        url: '/status?process=' + element.attr('id'),
        dataType: 'json',
        success: function (data) { /* update progress bar and change
messages */ }
    }, 1000);

Unfortunately, when this script is run from nginx, the above progress
request never even finishes a single request until *after* the first
request that sent the data gets it's own response.

Basically, it appears that the nginx server can only handle 1 open
at a time on Windows. I don't have this problem at all on Linux

Is there anyway to configure nginx so I can use it on my local Windows
development server?

Posted at Nginx Forum:,252695,252695#msg-252695
2974d09ac2541e892966b762aad84943?d=identicon&s=25 itpp2012 (Guest)
on 2014-08-20 17:12
(Received via mailing list)
eComEvo Wrote:
> This call will start a background process and it waits for it to
> complete so it can display the final result.

This is called blocking (as I already wrote on stack), to run this
nonblocking your probably going to need cosockets and in order to
any such solution we need to see a complete config in order to replicate

Posted at Nginx Forum:,252695,252696#msg-252696
This topic is locked and can not be replied to.