DRB/dRuby server throws an exception when probed on its port
I am not sure if this is a bug or a feature ...
When I use nmap to probe the port that the DRB server is listening on, it throws an exception.
Should the server be more resilient to this and/or have an option to restart itself automatically?
Or is the last code sample I give the suggested usage.
See this stackoverflow issue for sample code and little more info - http://stackoverflow.com/questions/15256619/druby-server-crashes-when-probed-on-the-port-its-listening-on?noredirect=1#comment21525295_15256619
Updated by jeremyevans (Jeremy Evans) 8 months ago
- Status changed from Assigned to Closed
Applied in changeset git|567e312d1f56c27ecb4fa20deac4311f05ee5507.
Do not raise an exception on a closed DRb socket
This rescues some exceptions that could happen with a closed or
shutdown DRb socket. This can prevent the server from
exiting if an client socket is closed directly after it is
Fixes [Bug #8039]