#2189 - Removing RemoteClientWriteFailed and log it as a RemoteClientError and send the message to DeadLetters
This commit is contained in:
parent
4d3e9f19fe
commit
211435048a
4 changed files with 8 additions and 29 deletions
|
|
@ -280,10 +280,6 @@ which holds the transport used (RemoteTransport) and the outbound address that i
|
|||
To intercept when an outbound client is shut down you listen to ``RemoteClientShutdown``
|
||||
which holds the transport used (RemoteTransport) and the outbound address that it was connected to (Address).
|
||||
|
||||
To intercept when an outbound message cannot be sent, you listen to ``RemoteClientWriteFailed`` which holds
|
||||
the payload that was not written (AnyRef), the cause of the failed send (Throwable),
|
||||
the transport used (RemoteTransport) and the outbound address that was the destination (Address).
|
||||
|
||||
For general outbound-related errors, that do not classify as any of the others, you can listen to ``RemoteClientError``,
|
||||
which holds the cause (Throwable), the transport used (RemoteTransport) and the outbound address (Address).
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue