By default, the backlog on the TCP serversocket is set to 50, and given that the accept is taking less than 50ms, I can't see that the server side is a problem.
You are not, by any chance, using the h2.bindAddress setting, are you? Because in that case it looks like we have a bug where we are setting the backlog to zero. What operating system are you using? This might be some kind of DNS or local name resolver issue. You could try running Wireshark and logging local timestamp and the port numbers from both ends of the socket, and then looking in wireshark to see what is happening to the failed connections. -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
