+972 52-548-6969
Solve this bug!
time to read 1 min | 72 words
This took some head scratching before I figured it out.
And here is the relevant code:
FUTURE POSTS
- Querying over the current time in RavenDB - 2 hours from now
There are posts all the way to Oct 11, 2024
RECENT SERIES
-
Challenge
(75):
01 Jul 2024 - Efficient snapshotable state -
Recording
(14):
19 Jun 2024 - Building a Database Engine in C# & .NET -
re
(33):
28 May 2024 - Secure Drop protocol -
Meta Blog
(2):
23 Jan 2024 - I'm a JS Developer now -
Production Postmortem
(51):
12 Dec 2023 - The Spawn of Denial of Service
RECENT COMMENTS
-
By cuadro personalizado on Debugging the Linux kernel using awesome psychic powers
-
By Adam on Debugging the Linux kernel using awesome psychic powers
-
Tһis page ceｒtainly hһas аll the information I needｅd about this subject ɑnd didn't know who to ask.By regalos personalizados on Seeing the results of Corax in production
-
By seo ser on Seeing the results of Corax in production
-
By liga novia on Seeing the results of Corax in production
Syndication
| Main feed | |
| Comments feed |
Comments
Race condition between creating the TcpListener and starting it and multiple threads calling this code at the same time.
Solution: lock around new TcpListener and tcpListener.Start().
RAGE... I hate when people do find available port by iterating and catching exceptions. The correct way to do this is:
listener = new TcpListener(IPAddress.Loopback, 0); //
RTFMMSDN listener.Start(); port = ((IPEndPoint)listener.LocalEndpoint).Port;Let the OS do it's work.
@hazzik wow, goes to say that sometimes RTFM is the best answer :-).
Try run this code: https://gist.github.com/hazzik/edd28a7129f820b4579b
How many exceptions!?! Zero.
I got six exception when I ran it with Linqpad
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full [Source = Worker Thread]
Giorgi they are all unrelated to the problem, it is just because it tries to spawn 1000 threads
@hazzik the nuance is that the proxy is trying to create a listener within a known range: 1 - port AFAIK, you do not have this when using 0 as a port
Signature of the constructor is different between stack and code. You're running old code?
You have another constructor ProxyServer(int port, int to) that do not catch SocketException?
As Jahmai points out the stacktrace shows ProxyServer..ctor(Int32 from, Int32 to) and not ProxyServer..ctor(Int32& from, Int32 to).
Jahmai, DING DING DING, yes, that is the issue
Comment preview