Files
nats-server/server/configs/test.conf
Ivan Kozlovic d2578f9e05 Update to connect/reconnect error reports logic
Changed the introduced new option and added a new one. The idea
is to be able to differentiate between never connected and reconnected
event. The never connected situation will be logged at first attempt
and every hour (by default, configurable).
However, once connected and if trying to reconnect, will report every
attempts by default, but this is configurable too.

These two options are supported for config reload.

Related to #1000
Related to #1001
Resolves #969

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
2019-05-26 17:51:01 -06:00

55 lines
904 B
Plaintext

# Simple config file
listen: 127.0.0.1:4242
http: 8222
authorization {
user: derek
password: porkchop
timeout: 1
}
# logging options
debug: false
trace: true
logtime: false
syslog: true
remote_syslog: "udp://foo.com:33"
# pid file
pid_file: "/tmp/nats-server.pid"
# prof_port
prof_port: 6543
# max_connections
max_connections: 100
# max_subscriptions (per connection)
max_subscriptions: 1000
# max_pending
max_pending: 10000000
# maximum control line
max_control_line: 2048
# maximum payload
max_payload: 65536
# ping interval and no pong threshold
ping_interval: 60
ping_max: 3
# how long server can block on a socket write to a client
write_deadline: "3s"
lame_duck_duration: "4m"
# report repeated failed route/gateway/leafNode connection
# every 24hour (24*60*60)
connect_error_reports: 86400
# report failed reconnect events every 5 attempts
reconnect_error_reports: 5