Exceptions cause DRb connection to be closed
If an exception is thrown in a DRb server of a class that is not defined in the client process, the DRb connection is closed abrubtly. In Ruby 1.8, the exception was translated to an instance generic exception class (DRb::DRbRemoteError).
Steps to reproduce:
- Start DRb client+server
- Throw exception of custom class in server (class not defined in client script).
- Client raises DRb::DRbConnError because connection is closed - used to be generic error.
- Client raises DRb::DRbRemoteError, and preserves full stack trace from server.
Attached is server/client script showing the problem.
Here is the stack trace of the client:
load': connection closed (DRb::DRbConnError)recv_reply'
block (2 levels) in method_missing'open'
block in method_missing'with_friend'
Updated by jeremyevans0 (Jeremy Evans) about 1 year ago
This issue is unrelated to whether the client defines the same exception class as the server, and the behavior in my testing appears to be the same on 1.8 as in the master branch.
The underlying issue is that the example code here uses a subclass of
DRb::DRbServer::InvokeMethod#perform does not rescue
Exception. Attached is a patch that fixes this issue.
Updated by jeremyevans (Jeremy Evans) 10 months ago
- Status changed from Assigned to Closed
Applied in changeset git|50b8033d6b7404670ee985de1473fffc10dd7d9c.
Handle subclasses of Exception in drb
This makes it so that client instances that call a method on a
server-side object that raise a subclass of Exception are handled
similarly to those that raise a subclass of StandardError.
Only reraise exceptions that we are fairly sure we don't want to
Fixes [Bug #5618]