Server built on Windows not handling simultaneous requests

[issue-up]

Forwarded from downstream issue: Server built on Windows not handling simultaneous requests nuxt/nuxt#15164 by @JeffreyTan1

Environment

• Operating System: Windows_NT
• Node Version: v16.16.0
• Nuxt Version: 3.0.0-rc.11
• Nitro Version: 0.5.4
• Package Manager: yarn@1.22.19
• Builder: vite
• User Config: modules, privateRuntimeConfig, publicRuntimeConfig, build, vite, typescript, dev
• Runtime Modules: @pinia/nuxt@0.4.2, @nuxtjs/tailwindcss@5.3.3
• Build Modules: -

Reproduction

• Clone https://github.com/JeffreyTan1/nuxt-bug-reproduction

I scaffolded the project like so https://v3.nuxtjs.org/getting-started/installation/ and the api from here https://v3.nuxtjs.org/guide/directory-structure/server/

• I use JMeter to simulate multiple users hitting the server at once. You can get JMeter from here: https://archive.apache.org/dist/jmeter/binaries/ I have the distribution found at apache-jmeter-5.4.3.zip.

As a quick tutorial of how to setup a JMeter stress test on Windows:

• Unzip the download
• Go into the bin folder
• Open the ApacheJMeter JAR file (opens the GUI)
• Create thread group and set the following properties.
• Create a HTTP Request sampler and set the following properties
• Create a View Results Tree listener and stay in this window
• Click the green play button to run the test and the gear+broomstick button to clear the output

You should see 200 responses interspersed by 503 responses.

Describe the bug

The Nuxt server is not handling simultaneous requests and is only happening on Windows.

Sometimes, when two or more requests hit the server at the same time, only one of them gets served, and the other requests return with a 503 Server Unavailable response instead of being added to the queue.

I have tested on ARM and Intel MacOS systems as well as WSL - all of which do not have the same problem. I have also tried Node v14.16 and LTS (v16.17.1).

This seems to me like a very low-level framework issue. The last version of Nuxt3 I've used is 'nuxt3': 3.0.0-27376943.f219f63 which did not have this problem.

Additional context

No response

Logs

No response

[Hebilicious]

#1115 did not fix the issue succesfully

[pi0]

@Hebilicious Needs minimal nitro reproduction to track here!

[pi0]

~> hhttps://github.com//issues/1454