2011-11-15 11:34:39 +01:00
|
|
|
#####################################
|
|
|
|
|
# Akka Remote Reference Config File #
|
|
|
|
|
#####################################
|
|
|
|
|
|
|
|
|
|
# This the reference config file has all the default settings.
|
2011-12-14 15:12:40 +01:00
|
|
|
# Make your edits/overrides in your application.conf.
|
2011-11-15 11:34:39 +01:00
|
|
|
|
|
|
|
|
akka {
|
|
|
|
|
|
2011-12-12 23:31:15 +01:00
|
|
|
actor {
|
|
|
|
|
|
2012-02-06 21:12:26 +01:00
|
|
|
# Entries for pluggable serializers and their bindings.
|
|
|
|
|
serializers {
|
|
|
|
|
proto = "akka.serialization.ProtobufSerializer"
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Class to Serializer binding. You only need to specify the name of an interface
|
2012-02-07 15:11:16 +01:00
|
|
|
# or abstract base class of the messages. In case of ambiguity it is
|
|
|
|
|
# using the most specific configured class, giving an error if two mappings are found
|
|
|
|
|
# which cannot be decided by sub-typing relation.
|
2012-02-06 21:12:26 +01:00
|
|
|
serialization-bindings {
|
2012-02-07 15:11:16 +01:00
|
|
|
# Since com.google.protobuf.Message does not extend Serializable but GeneratedMessage
|
|
|
|
|
# does, need to use the more specific one here in order to avoid ambiguity
|
|
|
|
|
"com.google.protobuf.GeneratedMessage" = proto
|
2012-02-06 21:12:26 +01:00
|
|
|
}
|
|
|
|
|
|
2011-12-12 23:31:15 +01:00
|
|
|
deployment {
|
|
|
|
|
|
|
|
|
|
default {
|
|
|
|
|
|
2011-12-15 14:26:17 +01:00
|
|
|
# if this is set to a valid remote address, the named actor will be deployed
|
|
|
|
|
# at that node e.g. "akka://sys@host:port"
|
2011-12-14 15:12:40 +01:00
|
|
|
remote = ""
|
2011-12-12 23:31:15 +01:00
|
|
|
|
2012-01-17 08:44:46 +01:00
|
|
|
target {
|
2011-12-14 15:12:40 +01:00
|
|
|
|
2011-12-15 14:26:17 +01:00
|
|
|
# A list of hostnames and ports for instantiating the children of a
|
|
|
|
|
# non-direct router
|
2011-12-14 15:12:40 +01:00
|
|
|
# The format should be on "akka://sys@host:port", where:
|
|
|
|
|
# - sys is the remote actor system name
|
2011-12-15 14:26:17 +01:00
|
|
|
# - hostname can be either hostname or IP address the remote actor
|
|
|
|
|
# should connect to
|
2011-12-14 15:12:40 +01:00
|
|
|
# - port should be the port for the remote server on the other node
|
2011-12-15 14:26:17 +01:00
|
|
|
# The number of actor instances to be spawned is still taken from the
|
|
|
|
|
# nr-of-instances setting as for local routers; the instances will be
|
|
|
|
|
# distributed round-robin among the given nodes.
|
2011-12-14 15:12:40 +01:00
|
|
|
nodes = []
|
|
|
|
|
|
2011-12-12 23:31:15 +01:00
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2011-11-15 11:34:39 +01:00
|
|
|
remote {
|
2011-12-30 17:24:23 +01:00
|
|
|
|
2012-01-20 14:29:50 +01:00
|
|
|
# Which implementation of akka.remote.RemoteTransport to use
|
2011-12-30 17:24:23 +01:00
|
|
|
# default is a TCP-based remote transport based on Netty
|
2012-01-20 14:29:50 +01:00
|
|
|
transport = "akka.remote.netty.NettyRemoteTransport"
|
2011-11-25 12:02:25 +01:00
|
|
|
|
2012-01-20 14:29:50 +01:00
|
|
|
# Enable untrusted mode for full security of server managed actors, allows
|
|
|
|
|
# untrusted clients to connect.
|
|
|
|
|
untrusted-mode = off
|
2011-11-15 11:34:39 +01:00
|
|
|
|
2011-12-14 15:12:40 +01:00
|
|
|
# Timeout for ACK of cluster operations, lik checking actor out etc.
|
|
|
|
|
remote-daemon-ack-timeout = 30s
|
2011-11-15 11:34:39 +01:00
|
|
|
|
2012-01-21 00:32:37 +01:00
|
|
|
# If this is "on", Akka will log all inbound messages at DEBUG level, if off then they are not logged
|
|
|
|
|
log-received-messages = off
|
|
|
|
|
|
|
|
|
|
# If this is "on", Akka will log all outbound messages at DEBUG level, if off then they are not logged
|
|
|
|
|
log-sent-messages = off
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# Each property is annotated with (I) or (O) or (I&O), where I stands for “inbound” and O for “outbound” connections.
|
2012-01-20 14:29:50 +01:00
|
|
|
# The NettyRemoteTransport always starts the server role to allow inbound connections, and it starts
|
|
|
|
|
# active client connections whenever sending to a destination which is not yet connected; if configured
|
|
|
|
|
# it reuses inbound connections for replies, which is called a passive client connection (i.e. from server
|
|
|
|
|
# to client).
|
|
|
|
|
netty {
|
2012-01-30 19:57:05 +01:00
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (O) In case of increased latency / overflow how long
|
2012-01-20 14:29:50 +01:00
|
|
|
# should we wait (blocking the sender) until we deem the send to be cancelled?
|
|
|
|
|
# 0 means "never backoff", any positive number will indicate time to block at most.
|
|
|
|
|
backoff-timeout = 0ms
|
2012-01-30 19:57:05 +01:00
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I&O) Generate your own with '$AKKA_HOME/scripts/generate_config_with_secure_cookie.sh'
|
2012-01-20 14:29:50 +01:00
|
|
|
# or using 'akka.util.Crypt.generateSecureCookie'
|
|
|
|
|
secure-cookie = ""
|
2012-01-30 19:57:05 +01:00
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) Should the remote server require that it peers share the same secure-cookie
|
2012-01-20 14:29:50 +01:00
|
|
|
# (defined in the 'remote' section)?
|
|
|
|
|
require-cookie = off
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) Reuse inbound connections for outbound messages
|
2012-01-20 14:29:50 +01:00
|
|
|
use-passive-connections = on
|
2012-01-30 19:57:05 +01:00
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) The hostname or ip to bind the remoting to,
|
2012-01-20 14:29:50 +01:00
|
|
|
# InetAddress.getLocalHost.getHostAddress is used if empty
|
|
|
|
|
hostname = ""
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) The default remote server port clients should connect to.
|
2012-01-20 14:29:50 +01:00
|
|
|
# Default is 2552 (AKKA), use 0 if you want a random available port
|
|
|
|
|
port = 2552
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I&O) Increase this if you want to be able to send messages with large payloads
|
2012-01-20 14:29:50 +01:00
|
|
|
message-frame-size = 1 MiB
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (O) Timeout duration
|
2012-01-20 14:29:50 +01:00
|
|
|
connection-timeout = 120s
|
2011-11-15 11:34:39 +01:00
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) Sets the size of the connection backlog
|
2012-01-20 14:29:50 +01:00
|
|
|
backlog = 4096
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) Length in akka.time-unit how long core threads will be kept alive if idling
|
2012-01-20 14:29:50 +01:00
|
|
|
execution-pool-keepalive = 60s
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) Size of the core pool of the remote execution unit
|
2012-01-20 14:29:50 +01:00
|
|
|
execution-pool-size = 4
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) Maximum channel size, 0 for off
|
2012-01-20 14:29:50 +01:00
|
|
|
max-channel-memory-size = 0b
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (I) Maximum total size of all channels, 0 for off
|
2012-01-20 14:29:50 +01:00
|
|
|
max-total-memory-size = 0b
|
|
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (O) Time between reconnect attempts for active clients
|
2012-01-20 14:29:50 +01:00
|
|
|
reconnect-delay = 5s
|
|
|
|
|
|
2012-02-01 16:06:30 +01:00
|
|
|
# (O) Read inactivity period (lowest resolution is seconds)
|
|
|
|
|
# after which active client connection is shutdown;
|
|
|
|
|
# will be re-established in case of new communication requests.
|
|
|
|
|
# A value of 0 will turn this feature off
|
|
|
|
|
read-timeout = 0s
|
|
|
|
|
|
|
|
|
|
# (O) Write inactivity period (lowest resolution is seconds)
|
2012-02-01 16:20:51 +01:00
|
|
|
# after which a heartbeat is sent across the wire.
|
2012-02-01 16:06:30 +01:00
|
|
|
# A value of 0 will turn this feature off
|
|
|
|
|
write-timeout = 10s
|
|
|
|
|
|
|
|
|
|
# (O) Inactivity period of both reads and writes (lowest resolution is seconds)
|
|
|
|
|
# after which active client connection is shutdown;
|
|
|
|
|
# will be re-established in case of new communication requests
|
|
|
|
|
# A value of 0 will turn this feature off
|
|
|
|
|
all-timeout = 0s
|
2012-01-20 14:29:50 +01:00
|
|
|
|
2012-01-30 11:48:02 +01:00
|
|
|
# (O) Maximum time window that a client should try to reconnect for
|
2012-01-20 14:29:50 +01:00
|
|
|
reconnection-time-window = 600s
|
|
|
|
|
}
|
2012-01-18 18:10:56 +01:00
|
|
|
|
2011-12-20 21:08:27 +01:00
|
|
|
# The dispatcher used for the system actor "network-event-sender"
|
|
|
|
|
network-event-sender-dispatcher {
|
2012-02-07 09:50:03 +01:00
|
|
|
executor = thread-pool-executor
|
2011-12-20 21:08:27 +01:00
|
|
|
type = PinnedDispatcher
|
|
|
|
|
}
|
2011-11-15 11:34:39 +01:00
|
|
|
}
|
|
|
|
|
}
|