From: "drbrain (Eric Hodel)" <drbrain@...7.net>
Date: 2013-03-11T13:43:02+09:00
Subject: [ruby-core:53313] [ruby-trunk - Bug #8039] DRB/dRuby server throws an exception when probed on its port


Issue #8039 has been updated by drbrain (Eric Hodel).

File drb.socket_shutdown_fix.patch added
Target version set to current: 2.1.0

This patch fixes the bug.
----------------------------------------
Bug #8039: DRB/dRuby server throws an exception when probed on its port
https://bugs.ruby-lang.org/issues/8039#change-37495

Author: kimptoc (Chris Kimpton)
Status: Assigned
Priority: Normal
Assignee: seki (Masatoshi Seki)
Category: lib
Target version: current: 2.1.0
ruby -v: 1.9.3-p392 and jruby 1.7.3


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


-- 
http://bugs.ruby-lang.org/