[
https://issues.apache.org/jira/browse/LOG4J2-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156731#comment-15156731
]
Mikael Ståldal edited comment on LOG4J2-1290 at 2/22/16 10:35 AM:
------------------------------------------------------------------
The important thing is to define the semantics of timeout, what to do when the
timeout expires?
Using Netty or not is just an implementation detail.
And when we have agreed about semantics and added timeout to SocketAppender, we
should add similar timeout, with the same semantics, to other relevant
appenders (KafkaAppender, SMTPAppender, NoSQLAppdender, JMSAppender,
ZeroMQAppender, maybe FlumeAppender).
was (Author: mikaelstaldal):
The important thing is to define the semantics of timeout, what to do when the
timeout expires?
Using Netty or not is just an implementation detail.
> Add SoTimeout value config support when use SocketAppender
> ----------------------------------------------------------
>
> Key: LOG4J2-1290
> URL: https://issues.apache.org/jira/browse/LOG4J2-1290
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: zhaoyufei
> Labels: SocketAppender
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Currently, when i use SocketAppdnder, for timeout related parameters,
> only connectTimeout is support.
> but i think it is better to make SoTimeout support also.
> If socket target server is busy some time, then socketAppender will take
> long time to wait for target's response, this can somehow slow client
> application speed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
