We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In de.siegmar.logbackgelf.GelfTcpAppender, the documentation for reconnectInterval says:
de.siegmar.logbackgelf.GelfTcpAppender
reconnectInterval
Time interval (in seconds) after an existing connection is closed and re-opened. A value of 0 disables automatic reconnects. Default: 300 seconds.
but the implementation checks for < 0, so effectively reconnects on every message:
private void connect() throws IOException { closeOut(); final Socket socket = getSocket(); outputStream = socket.getOutputStream(); nextReconnect = reconnectInterval < 0 ? Long.MAX_VALUE : System.currentTimeMillis() + (reconnectInterval * SEC_TO_MSEC); }
The text was updated successfully, but these errors were encountered:
Thanks! This has already been fixed in the connection-pool branch which is supposed to be released shortly.
Sorry, something went wrong.
fixed in 1.1.0 which has just been released
osiegmar
No branches or pull requests
In
de.siegmar.logbackgelf.GelfTcpAppender
, the documentation forreconnectInterval
says:but the implementation checks for < 0, so effectively reconnects on every message:
The text was updated successfully, but these errors were encountered: