move multi-node-testkit into its own module, see #2981
This commit is contained in:
parent
29b274b9c0
commit
c3b363c9b3
18 changed files with 103 additions and 33 deletions
|
|
@ -362,13 +362,18 @@ It is possible to listen to events that occur in Akka Remote, and to subscribe/u
|
|||
you simply register as listener to the below described types in on the ``ActorSystem.eventStream``.
|
||||
|
||||
.. note::
|
||||
To subscribe to any remote event, subscribe to :meth:``RemotingLifecycleEvent`
|
||||
To subscribe to events related only to the lifecycle of associations, subscribe to :meth:`akka.remote.AssociationEvent`
|
||||
|
||||
To subscribe to any remote event, subscribe to
|
||||
:meth:`RemotingLifecycleEvent`. To subscribe to events related only to the
|
||||
lifecycle of associations, subscribe to
|
||||
:meth:`akka.remote.AssociationEvent`.
|
||||
|
||||
.. note::
|
||||
The use of term "Association" instead of "Connection" reflects that the remoting subsystem may use
|
||||
connectionless transports, but an association similar to transport layer connections is maintained between endpoints
|
||||
by the Akka protocol.
|
||||
|
||||
The use of term "Association" instead of "Connection" reflects that the
|
||||
remoting subsystem may use connectionless transports, but an association
|
||||
similar to transport layer connections is maintained between endpoints by
|
||||
the Akka protocol.
|
||||
|
||||
By default an event listener is registered which logs all of the events
|
||||
described below. This default was chosen to help setting up a system, but it is
|
||||
|
|
@ -376,6 +381,7 @@ quite common to switch this logging off once that phase of the project is
|
|||
finished.
|
||||
|
||||
.. note::
|
||||
|
||||
In order to switch off the logging, set
|
||||
``akka.remote.log-remote-lifecycle-events = off`` in your
|
||||
``application.conf``.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue