[
https://issues.apache.org/jira/browse/LOG4J2-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156553#comment-15156553
]
zhaoyufei commented on LOG4J2-1290:
-----------------------------------
As from my work projects, there can be lots of log event,
for very little of them, maybe very slow to send to the target server because
of network issues.
so if very little log event timeout, then just dropped them to avoid them to
take up the quene.
If many slow log event take up all the quene, then the appender will block for
the quene.
also for further step, we can also add support to retryCount parameter to allow
to retry.
both the soTimeout and retryCount can be set by user according to their
different cases.
Just like the related parameters supported by HttpClient framework.
> 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]
