Issue #8039 has been reported by kimptoc (Chris Kimpton). ---------------------------------------- Bug #8039: DRB/dRuby server throws an exception when probed on its port https://bugs.ruby-lang.org/issues/8039 Author: kimptoc (Chris Kimpton) Status: Open Priority: Normal Assignee: Category: Target version: 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-... Thanks, Chris
on 2013-03-07 08:48
on 2013-03-09 00:18
Issue #8039 has been updated by drbrain (Eric Hodel). Category set to lib Status changed from Open to Assigned Assignee set to seki (Masatoshi Seki) ---------------------------------------- Bug #8039: DRB/dRuby server throws an exception when probed on its port https://bugs.ruby-lang.org/issues/8039#change-37405 Author: kimptoc (Chris Kimpton) Status: Assigned Priority: Normal Assignee: seki (Masatoshi Seki) Category: lib Target version: 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-... Thanks, Chris
on 2013-03-11 05:43
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-... Thanks, Chris
Enable email notification
Enable multi-page viewPlease log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.