[jboss-jira] [JBoss JIRA] (LOGMGR-113) Create a better way to handle a TCP reconnect policy

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/LOGMGR-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins updated LOGMGR-113:
---------------------------------
    Fix Version/s: 2.1.0.Beta1
                       (was: 2.0.0.Final)


> 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
>            Assignee: James Perkins
>             Fix For: 2.1.0.Beta1
>
>
> 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
(v6.3.15#6346)