TLS/TCP connection errors due to timeout

[robertvazan]

I am using logback-syslog4j and it prints the following error to console whenever I log some message after a period of inactivity (a few minutes of no logging):

SSLTCPNetSyslog: DOWN (org.productivity.java.syslog4j.SyslogRuntimeException: java.net.SocketException: Software caused connection abort: socket write error)
INFO <14>Oct  2 21:24:10 HorsePower viewbox: INFO  ServerConnector: Stopped ServerConnector@43bd930a{HTTP/1.1,[http/1.1]}{127.0.0.1:8080}
 [org.productivity.java.syslog4j.SyslogRuntimeException: java.net.SocketException: Software caused connection abort: socket write error]
SSLTCPNetSyslog: UP

So whenever I log a burst of say 10 messages, only 9 of them will make it to the syslog server (papertrail in this case). The first log message is lost. Solo messages are lost altogether.

Is there any setting I can tweak to keep the connection alive or to make logback retry the failed log message?

[liskin]

It seems like a hack, but setting /proc/sys/net/ipv4/tcp_keepalive_time to less than 2 hours may help.