Skip to main content

Solving the "Synchronous operations are disallowed" Exception in ASP.NET Core

After making a small change to an ASP.NET core application, I got the following runtime error:

System.InvalidOperationException: 'Synchronous operations are disallowed. Call ReadAsync or set AllowSynchronousIO to true instead.'

Here is the code that caused the error:

Let's explore why this happens, when it occurs, and most importantly, how to fix it properly.

Why does this exception occur?

Starting with ASP.NET Core 3.0, Microsoft made a significant architectural change: synchronous I/O operations are disabled by default on the server. This decision was made to improve application performance and prevent thread pool starvation.

In traditional synchronous I/O operations, threads are blocked while waiting for data to be read or written. In a web server handling hundreds or thousands of concurrent requests, this can quickly exhaust the thread pool, leading to:

  • Poor scalability
  • Increased response times
  • Potential deadlocks
  • Resource exhaustion

Asynchronous I/O operations release threads back to the thread pool while waiting for I/O operations to complete, allowing the server to handle more concurrent requests with fewer resources avoiding all the issues above.

Solutions: The right way vs. The quick fix

The right way to fix this is by switching to an async version of our code:

If an async alternative is not available and you really want to use synchronous operations, you can enable this globally or at the request level:

More information

Breaking changes in .NET Core 3.0 - .NET | Microsoft Learn

Configure options for the ASP.NET Core Kestrel web server | Microsoft Learn

Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more