From 48ca56459ee5fa4cd2d75c4a388835b085aea66f Mon Sep 17 00:00:00 2001 From: Roland Date: Fri, 17 Aug 2012 12:25:31 +0200 Subject: [PATCH] switch remoting logging on by default, see #2397 --- akka-docs/java/remoting.rst | 10 ++++++++++ akka-docs/scala/remoting.rst | 10 ++++++++++ akka-remote/src/main/resources/reference.conf | 3 ++- 3 files changed, 22 insertions(+), 1 deletion(-) diff --git a/akka-docs/java/remoting.rst b/akka-docs/java/remoting.rst index d00eb02dc7..07ebd6e36a 100644 --- a/akka-docs/java/remoting.rst +++ b/akka-docs/java/remoting.rst @@ -274,6 +274,16 @@ you simply register as listener to the below described types in on the ``ActorSy To subscribe to any inbound-related events, subscribe to ``RemoteServerLifeCycleEvent`` To subscribe to any remote events, subscribe to ``RemoteLifeCycleEvent`` +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 +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``. + To intercept when an outbound connection is disconnected, you listen to ``RemoteClientDisconnected`` which holds the transport used (RemoteTransport) and the outbound address that was disconnected (Address). diff --git a/akka-docs/scala/remoting.rst b/akka-docs/scala/remoting.rst index 6a0e8731b7..b22626f67f 100644 --- a/akka-docs/scala/remoting.rst +++ b/akka-docs/scala/remoting.rst @@ -278,6 +278,16 @@ you simply register as listener to the below described types in on the ``ActorSy To subscribe to any inbound-related events, subscribe to ``RemoteServerLifeCycleEvent`` To subscribe to any remote events, subscribe to ``RemoteLifeCycleEvent`` +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 +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``. + To intercept when an outbound connection is disconnected, you listen to ``RemoteClientDisconnected`` which holds the transport used (RemoteTransport) and the outbound address that was disconnected (Address). diff --git a/akka-remote/src/main/resources/reference.conf b/akka-remote/src/main/resources/reference.conf index 7ae3219c5d..45179796e1 100644 --- a/akka-remote/src/main/resources/reference.conf +++ b/akka-remote/src/main/resources/reference.conf @@ -72,7 +72,8 @@ akka { log-sent-messages = off # If this is "on", Akka will log all RemoteLifeCycleEvents at the level defined for each, if off then they are not logged - log-remote-lifecycle-events = off + # Failures to deserialize received messages also fall under this flag. + log-remote-lifecycle-events = on # Each property is annotated with (I) or (O) or (I&O), where I stands for “inbound” and O for “outbound” connections. # The NettyRemoteTransport always starts the server role to allow inbound connections, and it starts