[jboss-jira] [JBoss JIRA] (LOGMGR-113) Create a better way to handle a TCP reconnect policy
James Perkins (JIRA)
issues at jboss.org
Mon Oct 2 14:03:00 EDT 2017
[ https://issues.jboss.org/browse/LOGMGR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Perkins updated LOGMGR-113:
---------------------------------
Fix Version/s: (was: 2.1.0.Alpha5)
> Create a better way to handle a TCP reconnect policy
> ----------------------------------------------------
>
> Key: LOGMGR-113
> URL: https://issues.jboss.org/browse/LOGMGR-113
> Project: JBoss Log Manager
> Issue Type: Enhancement
> Reporter: James Perkins
>
> The audit logger in WildFly uses it's own policy to reconnect a TCP connection for the {{SyslogHandler}}. The current {{org.jboss.logmanager.handlers.TcpOutputStream}} handles a reconnection on it's own unless a deprecated constructor is used. A way to set some kind of policy or enable the reconnection to be turned off should be added.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list