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 "Gary Gregory (JIRA)" <ji...@apache.org> on 2016/11/14 07:20:58 UTC
[jira] [Created] (LOG4J2-1708) Allow Secure Socket Appender to set
socket options
Gary Gregory created LOG4J2-1708:
------------------------------------
Summary: Allow Secure Socket Appender to set socket options
Key: LOG4J2-1708
URL: https://issues.apache.org/jira/browse/LOG4J2-1708
Project: Log4j 2
Issue Type: New Feature
Components: Core
Reporter: Gary Gregory
Assignee: Gary Gregory
Allow any socket-based Appender to set socket options.
At the lowest level, this means that if configured the following {{java.net.Socket}} options are called:
- java.net.Socket.setKeepAlive(boolean)
- java.net.Socket.setOOBInline(boolean)
- java.net.Socket.setPerformancePreferences(int, int, int)
- java.net.Socket.setReceiveBufferSize(int)
- java.net.Socket.setReuseAddress(boolean)
- java.net.Socket.setSendBufferSize(int)
- java.net.Socket.setSoLinger(boolean, int)
- java.net.Socket.setSoTimeout(int)
- java.net.Socket.setTcpNoDelay(boolean)
- java.net.Socket.setTrafficClass(int)
This will done through a new {{SocketOptions}} XML element (same idea for JSON and YAML).
Another ticket will follow for SSL and Syslog.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org