able to accept 1K connections, and after that it can't accept more and
disconnects all connections, and starts going into this weird state.
I wrote a small app (another Go app) that spawns clients and connects to
the server running on localhost. Everything goes well if the number of
clients are < 1K. However, once I bumped it up, it starts failing right
around 1020, which is suspiciously close to 1024. I need to know if it's
my code, which seems more likely, or some weird bug with Go TCP, but at
this point my code hasn't done anything yet.
This is the simplified version of my TCP server:
http://play.golang.org/p/_EJ9oNZ0Cv
It's very simple. It listens to a port, new connection comes in, store the
net.TCPConn object in an array.
I wrote another go program that spawns clients
http://play.golang.org/p/fsEirFIUqR
Now, run the server, run the clients, and notice connections will start
failing around 1020.
Could somebody please explain why this is the case?
--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.