+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
- Optimizing the cost of clearing a set - one day from now
- Scaling HNSW in RavenDB: Optimizing for inadequate hardware - 3 days from now
There are posts all the way to May 14, 2025
RECENT SERIES
-
RavenDB News
(2):
02 May 2025 - May 2025 -
Recording
(15):
30 Apr 2025 - Practical AI Integration with RavenDB -
Production Postmortem
(52):
07 Apr 2025 - The race condition in the interlock -
RavenDB
(13):
02 Apr 2025 - .NET Aspire integration -
RavenDB 7.1
(6):
18 Mar 2025 - One IO Ring to rule them all
RECENT COMMENTS
-
By Samyon Ristov on The null check that didn't check for nulls
-
By Johannes Egger on The null check that didn't check for nulls
-
By riccardo on The null check that didn't check for nulls
-
By Chris B on The null check that didn't check for nulls
-
By Tim on When racing the Heisenbug, code quality goes out the Windows
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