Project

General

Profile

Bug #8039

DRB/dRuby server throws an exception when probed on its port

Added by kimptoc (Chris Kimpton) over 4 years ago. Updated over 3 years ago.

Status:
Assigned
Priority:
Normal
Target version:
ruby -v:
1.9.3-p392 and jruby 1.7.3
Backport:
[ruby-core:53186]

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

drb.socket_shutdown_fix.patch (1.03 KB) drb.socket_shutdown_fix.patch drbrain (Eric Hodel), 03/11/2013 01:43 PM

History

#1 [ruby-core:53246] Updated by drbrain (Eric Hodel) over 4 years ago

  • Category set to lib
  • Status changed from Open to Assigned
  • Assignee set to seki (Masatoshi Seki)

#2 [ruby-core:53313] Updated by drbrain (Eric Hodel) over 4 years ago

This patch fixes the bug.

#3 [ruby-core:60284] Updated by hsbt (Hiroshi SHIBATA) over 3 years ago

  • Target version changed from 2.1.0 to 2.2.0

Also available in: Atom PDF