Page Title: Xeon Productions – Programming the dreams of the future

Page Description:

Page Keywords:

Page Text: by Brandon So I was attempting to make use of IO completion ports and build a high performance socket server in C# by making use of the *Async methods such as ReceiveAsync with SocketAsyncEventArgs . However I’ve encountered a problem which I cannot seem to find a solution for which involves a StackOverException being triggered by the execution of these methods. You see, at first glance everything appeared to be humming along nicely, until I decided to flood my server with about 12,000 randomly sized packets. That’s when the problem shows up. I have a TryReceive method that makes the first call to ReceiveAsync , and if it returns FALSE, then I call the ProcessReceive directly, otherwise it gets called by the Completed event getting invoked on the SocketAsyncEventArgs . ProcessReceive then does some processing of the message and then calls TryReceive to start the process all over again. For whatever reason, the ReceiveAsync is always completing synchronously and creating a recursive loop with my two methods. I’m not really sure what to try at this point, other than possibly trying to call it on another thread, but I’m worried that might cause some other recursive thread call issues. If anyone has any ideas feel free to hit up my contact form. Here’s some extracted snippets of code to show how the calls are structured. private void TryReceive() { ... if (!Socket.ReceiveAsync(_receiveEventArg)) ProcessReceive(_receiveEventArg); ... } private void OnAsyncCompleted(object sender, SocketAsyncEventArgs e) { // Determine which type of operation just completed and call the associated handler switch (e.LastOperation) { case SocketAsyncOperation.Receive: ProcessReceive(e); break; case SocketAsyncOperation.Send: ProcessSend(e); break; default: throw new ArgumentException("The last operation completed on the socket was not a receive or send"); } } private void ProcessReceive(SocketAsyncEventArgs e) { ... if (e.SocketError == SocketError.Success) { // If zero is returned from a read operation, the remote end has closed the connection if (size > 0) TryReceive(); else Disconnect(); } } ... } 1

Header tags:

Your header tags:

Xeon Productions .NET Socket *Async methods have a design flaw. Updates I’m still alive! Attempting to write more code  GitHub Activity Free Development Tools Useful Sites 

Spelling errors:

Possibly mis-spelt word: Async

Suggestion: Sync
Suggestion: A sync

Possibly mis-spelt word: ReceiveAsync

Suggestion: Receivership

Possibly mis-spelt word: SocketAsyncEventArgs

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: Xeon Productions – Programming the dreams of the future

Page Description:

Page Keywords:

Page Text: by Brandon So I was attempting to make use of IO completion ports and build a high performance socket server in C# by making use of the *Async methods such as ReceiveAsync with SocketAsyncEventArgs . However I’ve encountered a problem which I cannot seem to find a solution for which involves a StackOverException being triggered by the execution of these methods. You see, at first glance everything appeared to be humming along nicely, until I decided to flood my server with about 12,000 randomly sized packets. That’s when the problem shows up. I have a TryReceive method that makes the first call to ReceiveAsync , and if it returns FALSE, then I call the ProcessReceive directly, otherwise it gets called by the Completed event getting invoked on the SocketAsyncEventArgs . ProcessReceive then does some processing of the message and then calls TryReceive to start the process all over again. For whatever reason, the ReceiveAsync is always completing synchronously and creating a recursive loop with my two methods. I’m not really sure what to try at this point, other than possibly trying to call it on another thread, but I’m worried that might cause some other recursive thread call issues. If anyone has any ideas feel free to hit up my contact form. Here’s some extracted snippets of code to show how the calls are structured. private void TryReceive() { ... if (!Socket.ReceiveAsync(_receiveEventArg)) ProcessReceive(_receiveEventArg); ... } private void OnAsyncCompleted(object sender, SocketAsyncEventArgs e) { // Determine which type of operation just completed and call the associated handler switch (e.LastOperation) { case SocketAsyncOperation.Receive: ProcessReceive(e); break; case SocketAsyncOperation.Send: ProcessSend(e); break; default: throw new ArgumentException("The last operation completed on the socket was not a receive or send"); } } private void ProcessReceive(SocketAsyncEventArgs e) { ... if (e.SocketError == SocketError.Success) { // If zero is returned from a read operation, the remote end has closed the connection if (size > 0) TryReceive(); else Disconnect(); } } ... } 1

Header tags:

Your header tags:

Xeon Productions .NET Socket *Async methods have a design flaw. Updates I’m still alive! Attempting to write more code  GitHub Activity Free Development Tools Useful Sites 

Spelling errors:

Possibly mis-spelt word: Async

Suggestion: Sync
Suggestion: A sync

Possibly mis-spelt word: ReceiveAsync

Suggestion: Receivership

Possibly mis-spelt word: SocketAsyncEventArgs

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: About – Xeon Productions

Page Description:

Page Keywords:

Page Text: About About me My name is Brandon, I’ve been interested in computers since I was 13, and have taught myself various programming languages and scripting languages over the years including C#, Java, Visual Basic, VoiceXML, PHP, MySQL, HTML, CSS, JavaScript, Delphi (Pascal), C, and C++. I’ve also experimented with graphic design, web design, and Linux server administration. I also know my way around the inside of a computer and have built and repaired more computers than I can count, troubleshooted bad components, and removed troublesome malware. I’m currently employed at a consulting company working on a project that involves rewriting a Python back-end system into .NET Core, ASP.NET Core, and EntityFramework (backed by PostgreSQL). About this site I started this site in 2003 with the intent of putting my creations and knowledge up on the internet. I also wanted to create a learning resource by posting programming examples, tutorials, and application code. Programming Languages

Header tags:

Your header tags:

About me About this site Programming Languages Operating Systems Languages  GitHub Activity Free Development Tools Useful Sites 

Spelling errors:

Possibly mis-spelt word: VoiceXML

Suggestion: Voice XML
Suggestion: Voice-XML
Suggestion: Voicemail

Possibly mis-spelt word: PHP

Suggestion: PP
Suggestion: HP
Suggestion: PEP
Suggestion: PHI
Suggestion: PIP
Suggestion: PAP
Suggestion: POP
Suggestion: PUP
Suggestion: P HP
Suggestion: PHD
Suggestion: PH

Possibly mis-spelt word: MySQL

Suggestion: My SQL
Suggestion: My-SQL
Suggestion: Myself

Possibly mis-spelt word: CSS

Suggestion: CS
Suggestion: CUSS
Suggestion: ASS
Suggestion: COS
Suggestion: CPS
Suggestion: CS S
Suggestion: C'S

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: Reviews – Xeon Productions

Page Description:

Page Keywords:

Page Text: An error has occurred, which probably means the feed is down. Try again later. Free Development Tools

Header tags:

Your header tags:

Reviews  GitHub Activity Free Development Tools Useful Sites 

Spelling errors:

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: Contact – Xeon Productions

Page Description:

Page Keywords:

Page Text: An error has occurred, which probably means the feed is down. Try again later. Free Development Tools

Header tags:

Your header tags:

Contact  GitHub Activity Free Development Tools Useful Sites 

Spelling errors:

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: Sourcecode – Xeon Productions

Page Description:

Page Keywords:

Page Text: Click Here Description: This was a map editor for Pokémon Red, which was originally released for the GameBoy. This was mainly just made for learning purposes, I learned a lot about how certain map structures and graphics are stored in the game itself. I never completed support for editing objects on the maps such as items, people and sign post triggers. Java AP Programming Class Java Assignments Language:

Header tags:

Your header tags:

Sourcecode Visual C# (.NET v2.0/3.5/v4.0) VB.NET Delphi  GitHub Activity Free Development Tools Useful Sites These are all projects and classes I’ve coded at one point or another. 

Spelling errors:

Possibly mis-spelt word: GameBoy

Suggestion: Game Boy
Suggestion: Game-boy
Suggestion: Homeboy

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: Snippets – Xeon Productions

Page Description:

Page Keywords:

Page Text: Snippets C# BinaryReaderEx/BinaryWriterEx – Allows you to control whether or not the underlying stream is disposed of after you dispose of the BinaryReader or BinaryWriter object. Managing list files – These are some quick and dirty functions for loading and saving list files. Random Macro Function – This will take an input string with words inside brackets and replace them with a random word from the list. Unix timestamp helper functions – These functions should take care of the base essentials when dealing with Unix Timestamps in C#. Probability function – Generates true or false a given percentage of the time. PHP Reading files using PHP – Here I show 3 different methods for reading the lines out of a simple text file. C Simple List – This is a simple string list library I made in C. It shows how to use a struct, a dynamically sized pointer array and some file operations. © 2022 Xeon Productions • Built with GeneratePress

Header tags:

Your header tags:

Snippets 

Spelling errors:

Possibly mis-spelt word: BinaryReader

Suggestion: Binary Reader
Suggestion: Binary-reader
Suggestion: Breadwinner

Possibly mis-spelt word: BinaryWriter

Suggestion: Binary Writer
Suggestion: Binary-writer
Suggestion: Veterinary

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: Tutorials – Xeon Productions

Page Description:

Page Keywords:

Page Text: This should get you started when it comes to using PHP and MySQLi. © 2022 Xeon Productions • Built with GeneratePress

Header tags:

Your header tags:

Tutorials 

Spelling errors:

Possibly mis-spelt word: PHP

Suggestion: PP
Suggestion: HP
Suggestion: PEP
Suggestion: PHI
Suggestion: PIP
Suggestion: PAP
Suggestion: POP
Suggestion: PUP
Suggestion: P HP
Suggestion: PHD
Suggestion: PH

Possibly mis-spelt word: MySQLi

Suggestion: Myelitis

Possibly mis-spelt word: Xeon

Suggestion: Eon
Suggestion: Neon
Suggestion: Peon
Suggestion: Leon
Suggestion: Deon
Suggestion: X eon
Suggestion: Xe on
Suggestion: Xe-on
Suggestion: Xenon
Suggestion: Oxen

Possibly mis-spelt word: GeneratePress

Suggestion: Generate Press
Suggestion: Generate-press
Suggestion: Generates
Suggestion: Temperateness
Suggestion: Desperateness
Suggestion: Separateness

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: .NET Socket *Async methods have a design flaw. – Xeon Productions

Page Description:

Page Keywords:

Page Text: .NET Socket *Async methods have a design flaw. August 21, 2019 by Brandon So I was attempting to make use of IO completion ports and build a high performance socket server in C# by making use of the *Async methods such as ReceiveAsync with SocketAsyncEventArgs . However I’ve encountered a problem which I cannot seem to find a solution for which involves a StackOverException being triggered by the execution of these methods. You see, at first glance everything appeared to be humming along nicely, until I decided to flood my server with about 12,000 randomly sized packets. That’s when the problem shows up. I have a TryReceive method that makes the first call to ReceiveAsync , and if it returns FALSE, then I call the ProcessReceive directly, otherwise it gets called by the Completed event getting invoked on the SocketAsyncEventArgs . ProcessReceive then does some processing of the message and then calls TryReceive to start the process all over again. For whatever reason, the ReceiveAsync is always completing synchronously and creating a recursive loop with my two methods. I’m not really sure what to try at this point, other than possibly trying to call it on another thread, but I’m worried that might cause some other recursive thread call issues. If anyone has any ideas feel free to hit up my contact form. Here’s some extracted snippets of code to show how the calls are structured. private void TryReceive() { ... if (!Socket.ReceiveAsync(_receiveEventArg)) ProcessReceive(_receiveEventArg); ... } private void OnAsyncCompleted(object sender, SocketAsyncEventArgs e) { // Determine which type of operation just completed and call the associated handler switch (e.LastOperation) { case SocketAsyncOperation.Receive: ProcessReceive(e); break; case SocketAsyncOperation.Send: ProcessSend(e); break; default: throw new ArgumentException("The last operation completed on the socket was not a receive or send"); } } private void ProcessReceive(SocketAsyncEventArgs e) { ... if (e.SocketError == SocketError.Success) { // If zero is returned from a read operation, the remote end has closed the connection if (size > 0) TryReceive(); else Disconnect(); } } ... } 1

Header tags:

Your header tags:

.NET Socket *Async methods have a design flaw. Archives 

Spelling errors:

Possibly mis-spelt word: Async

Suggestion: Sync
Suggestion: A sync

Possibly mis-spelt word: ReceiveAsync

Suggestion: Receivership

Possibly mis-spelt word: SocketAsyncEventArgs

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?:

Page Title: Brandon – Xeon Productions

Page Description:

Page Keywords:

Page Text: by Brandon So I was attempting to make use of IO completion ports and build a high performance socket server in C# by making use of the *Async methods such as ReceiveAsync with SocketAsyncEventArgs . However I’ve encountered a problem which I cannot seem to find a solution for which involves a StackOverException being triggered by the execution of these methods. You see, at first glance everything appeared to be humming along nicely, until I decided to flood my server with about 12,000 randomly sized packets. That’s when the problem shows up. I have a TryReceive method that makes the first call to ReceiveAsync , and if it returns FALSE, then I call the ProcessReceive directly, otherwise it gets called by the Completed event getting invoked on the SocketAsyncEventArgs . ProcessReceive then does some processing of the message and then calls TryReceive to start the process all over again. For whatever reason, the ReceiveAsync is always completing synchronously and creating a recursive loop with my two methods. I’m not really sure what to try at this point, other than possibly trying to call it on another thread, but I’m worried that might cause some other recursive thread call issues. If anyone has any ideas feel free to hit up my contact form. Here’s some extracted snippets of code to show how the calls are structured. private void TryReceive() { ... if (!Socket.ReceiveAsync(_receiveEventArg)) ProcessReceive(_receiveEventArg); ... } private void OnAsyncCompleted(object sender, SocketAsyncEventArgs e) { // Determine which type of operation just completed and call the associated handler switch (e.LastOperation) { case SocketAsyncOperation.Receive: ProcessReceive(e); break; case SocketAsyncOperation.Send: ProcessSend(e); break; default: throw new ArgumentException("The last operation completed on the socket was not a receive or send"); } } private void ProcessReceive(SocketAsyncEventArgs e) { ... if (e.SocketError == SocketError.Success) { // If zero is returned from a read operation, the remote end has closed the connection if (size > 0) TryReceive(); else Disconnect(); } } ... } 1

Header tags:

Your header tags:

Brandon .NET Socket *Async methods have a design flaw. Updates I’m still alive! Attempting to write more code  GitHub Activity Free Development Tools Useful Sites 

Spelling errors:

Possibly mis-spelt word: Async

Suggestion: Sync
Suggestion: A sync

Possibly mis-spelt word: ReceiveAsync

Suggestion: Receivership

Possibly mis-spelt word: SocketAsyncEventArgs

Broken links:

Broken image links:

CSS over tables for layout?:

Last modified date:

Images that are being re-sized:

Images that are being re-sized:

Mobile friendly:

Links with no anchor text:

W3C Validation:

Print friendly?:

GZIP Compression enabled?: