Use REUSEADDR when starting tcp server about puma

[evanphx]

Is there a reason it should? Are you seeing a problem that would be solved by doing so?

[paneq]

Technically it should allow to bind to port even when it is in TIME_WAIT state what might happen because of crash or killed process. EventMachine mentions in its code comments that it helps with unexpected restarts. Otherwise there are problems with binding again for some time.

I also use Puma for testing communication with external application and Puma is started and shutdown in every acceptance test. The problem is that such quick on/off workout leaves the socket in TIME_WAIT state and puma server (playing the role of external webservice) cannot start on the same port in subsequent tests. REUSEADDR should fix that but as you can see from my gist it does not work well for me.

I had the same issue when using Webrick but it works fine on Thin (which uses EM which sets this option in C code directly instead of via Ruby code). I guess this option might not work at all in Ruby but it is also possible that I am doing something wrong. I was hoping that someone smarter could try to use it and tell me if it behaves correctly or not.