-
Notifications
You must be signed in to change notification settings - Fork 37
AppendToStreamAsync hangs in .NET Framework 4.8 #303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
do other APIs work, i.e. could it be a connectivity issue? |
Yes, other APIs work. For example |
Can you try forcing a regular append by passing user credentials? Try it with this simple example:
|
Hey @w1am , We tried that and we got this exception: |
The gRPC client with net48 uses WinHttpHandler internally to make http calls. However, this comes with certain requirements and restrictions as listed in Microsoft Documentation. Could you try setting e.g |
Same results. Batch append hangs and regular append throws the same exception. |
This is interesting. I don't have a windows server to test it on. But it works fine on my Windows 11. I will keep investingating. Can you try kurrent-io/KurrentDB#2707 (comment) |
On Windows 11, I can reproduce it as well. It doesn’t hang, but I get the same HTTP/1.1 exception as above. Can you tell me your local setup which works with .NET Framework 4.8? I have tried that solution from the comment and I still get the same exception. |
This is my server docker compose configuration:
and the code I used is:
Operating System |
Hey @w1am, We did some more testing and we made it work running .net framework 4.8 client on windows 11. As long as you have certificates in place, it works. However, it doesn't work on Windows Server 2019 and Windows Server 2022. My best guess why it doesn't work on Windows server is this
Source: https://learn.microsoft.com/en-us/aspnet/core/grpc/netstandard?view=aspnetcore-8.0#net-framework |
This is a regression from moving to Grpc.Net.Client correct? Would it be better to continue to use Grpc.Core until Grpc.Net.Client support catches up? As of now, there's not much point in EventStore.Client.Grpc targeting .NET Framework if it only supports Windows 11. I'd even argue that it creates a false impression that the EventStore .NET client is officially supported on Windows-based service deployments for .NET Framework. Is it at least possible to allow the choice between grpc dependencies to be configurable until Grpc.Net.Client reaches sufficient feature parity? |
Describe the bug
We're unable to
AppendToStreamAsync
in .NET Framework 4.8, on Windows Server 2022 Datacenter version 21H2.The EventStore we're running against is
21.10.8.0
, installed on Windows Server.To Reproduce
Steps to reproduce the behavior:
21.10.8.0
client.AppendToStreamAsync
request.Expected behavior
For events to be appended.
Actual behavior
The application hangs.
Config/Logs/Screenshots
Default configuration.
EventStore details
Additional context
Exactly same code, but compiled against .NET 6, works as expected.
The text was updated successfully, but these errors were encountered: