Bug #8039

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

Added by Chris Kimpton about 1 year ago. Updated 3 months ago.

[ruby-core:53186]
Status:Assigned
Priority:Normal
Assignee:Masatoshi Seki
Category:lib
Target version:current: 2.2.0
ruby -v:1.9.3-p392 and jruby 1.7.3 Backport:

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 Magnifier (1.03 KB) Eric Hodel, 03/11/2013 01:43 PM

History

#1 Updated by Eric Hodel about 1 year ago

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

#2 Updated by Eric Hodel about 1 year ago

This patch fixes the bug.

#3 Updated by Hiroshi SHIBATA 3 months ago

  • Target version changed from 2.1.0 to current: 2.2.0

Also available in: Atom PDF