[
https://issues.apache.org/jira/browse/LOG4J2-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Deboy updated LOG4J2-171:
-------------------------------
Issue Type: New Feature (was: Bug)
> Implement a reverse-connect socket appender (SocketHubAppender)
> ---------------------------------------------------------------
>
> Key: LOG4J2-171
> URL: https://issues.apache.org/jira/browse/LOG4J2-171
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: Scott Deboy
>
> A reverse-connect TCP-based appender is useful for networking purposes
> (appender side doesn't need to know who is connecting to it, and can support
> multiple connections), and events can be cached, so in the case of an error,
> the most recent X events can be sent to anyone connecting to the appender.
> This was implemented in log4j1.x, would be good to have in log4j2
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
