You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by "Scott Deboy (JIRA)" <ji...@apache.org> on 2013/02/28 05:27:12 UTC

[jira] [Created] (LOG4J2-171) Implement a reverse-connect socket appender (SocketHubAppender)

Scott Deboy created LOG4J2-171:
----------------------------------

             Summary: Implement a reverse-connect socket appender (SocketHubAppender)
                 Key: LOG4J2-171
                 URL: https://issues.apache.org/jira/browse/LOG4J2-171
             Project: Log4j 2
          Issue Type: Bug
            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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org