Yeah I'm trying to figure out how to get a concise example of this - my deepest apologies.
I did try it with default ListenAndServeTLS and it exhibited the same problem. There is no Hijack calls, x/net/ipv4. This is really pretty bare-bones http service. I'd say its about 100 reqs/sec on one interface and 20 on the other. - Greg On Tuesday, September 20, 2016 at 7:44:40 AM UTC-7, James Bardin wrote: > > It would really help if we had some complete code to reproduce the issue. > > It sounds like the server isn't closing connections, but with only these > simple handlers I don't see where that could happen. Are there any Hijack > calls, x/net/ipv4, or network related syscalls anywhere in your code? > > Does this only happen with your custom tls.Config, or can you reproduce > this with the default ListenAndServeTLS? > > What is the request rate you're seeing when things start to fail? > -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.