logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhaoyufei (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1290) Add SoTimeout value config support when use SocketAppender
Date Mon, 22 Feb 2016 12:31:18 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156837#comment-15156837

zhaoyufei commented on LOG4J2-1290:

how about such rule:

user can defined soTimeout according to their cases:
if user want to make sure log event not lost, then he can simplely leave the soTimeout default(0).
 But he should be aware that slow log event take up all quene.

but he can also consider another way:
specify the soTimeout to a value, once timeout happen, he can close current socket to retry
fix number times to resend.
also if he can bear little log event lost, he can not retry, just throw error and then continue
to process other log event.

> 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message