Do not disconnect when there's a 'send' error
Summary: Historically, RSocket used to raise an error when there was an error during send, most likely because the connection was dead. With WS, this is no longer the case. WS connection issues are raised through the according handlers. Reviewed By: passy Differential Revision: D37825821 fbshipit-source-id: 7fcda8cf26fb42eb0d8ca03b62482f11c931777f
This commit is contained in:
committed by
Facebook GitHub Bot
parent
706ad760dc
commit
860cf332e1
@@ -379,9 +379,6 @@ export default abstract class AbstractClient extends EventEmitter {
|
|||||||
});
|
});
|
||||||
}
|
}
|
||||||
} catch (error) {
|
} catch (error) {
|
||||||
// This is only called if the connection is dead. Not in expected
|
|
||||||
// and recoverable cases like a missing receiver/method.
|
|
||||||
this.disconnect();
|
|
||||||
reject(new Error('Unable to send, connection error: ' + error));
|
reject(new Error('Unable to send, connection error: ' + error));
|
||||||
}
|
}
|
||||||
} else {
|
} else {
|
||||||
|
|||||||
Reference in New Issue
Block a user