Large messages on .NET 6 fail to send
See original GitHub issueDescribe the bug
When transferring messages larger than 65535 bytes on .NET 6 the server throws an exception stating
Expected <number of sent> bytes but read 65536
Steps to reproduce the bug
Send the contents of a 1MB file over the channel and catch the exception
Same issue whether I send a serializable object or a standard string
Expected behavior
No response
Screenshots
No response
NuGet package version
No response
Platform
Console
IDE
Visual Studio 2022
Additional context
Seems to be related to this: https://github.com/HavenDV/H.Pipes/blob/9299ffd93b5518a7c06e7fe12529bf45dfd8809c/src/libs/H.Pipes/IO/PipeStreamReader.cs#L72
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:9 (3 by maintainers)
Top Results From Across the Web
[BUG] Message lost when attempting to send large batch of ...
Our error handler opens a new transaction, sends a copy of the incoming message to the error queue and acknowledges the incoming message....
Read more >Exceeded storage allocation. The server response was: 4.3 ...
If you're trying to send a larger message, the server will reject it. You have quite a few options, however:
Read more >Attachment size exceeds the allowable limit error - Outlook
Describes the circumstances surrounding an error that occurs when you add a large attachment to an email message in Outlook.
Read more >Improving .NET host error messages and supportability
NET 7 Preview 6, we've updated several error messages and commands like dotnet --info to provide more helpful information.
Read more >Cannot debug net6.0-macos Apps - Developer Community
When I hit debug, the following error is shown in the Terminal: Possible reasons for this include: * You misspelled a built-in dotnet...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Clarification, this happens when used on a local network. When transferring between computers. I have to divide the data into chunks through my add-on, and then collect it back on the other side.
sweet I’ll try it out!