Bug #8039
closed
DRB/dRuby server throws an exception when probed on its port
Description
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
Thanks,
Chris
Files
Updated by drbrain (Eric Hodel) over 12 years ago
- Category set to lib
- Status changed from Open to Assigned
- Assignee set to seki (Masatoshi Seki)
Updated by drbrain (Eric Hodel) over 12 years ago
- File drb.socket_shutdown_fix.patch drb.socket_shutdown_fix.patch added
- Target version set to 2.1.0
This patch fixes the bug.
Updated by hsbt (Hiroshi SHIBATA) over 11 years ago
- Target version changed from 2.1.0 to 2.2.0
Updated by naruse (Yui NARUSE) almost 8 years ago
- Target version deleted (
2.2.0)
Updated by jeremyevans0 (Jeremy Evans) about 6 years ago
- File drb-sockopt-8039.patch drb-sockopt-8039.patch added
This bug is still present in the master branch. I've updated drbrain's patch to apply to the master branch, including adding some additional exceptions to rescue.
Updated by jeremyevans (Jeremy Evans) about 6 years 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
accepted.
Fixes [Bug #8039]