[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990631#comment-13990631 ] Remko Popma commented on LOG4J2-628: Bryan, SocketServer has been refactored and

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13989899#comment-13989899 ] Bryan Hsueh commented on LOG4J2-628: Tested, and works, thanks. I see this message

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13990093#comment-13990093 ] Remko Popma commented on LOG4J2-628: Bryan, good to hear that. About the error, we are

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988595#comment-13988595 ] Bryan Hsueh commented on LOG4J2-628: Sorry, I don't use the RolloverAppender, so I'll

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988426#comment-13988426 ] Remko Popma commented on LOG4J2-628: Understood. We are thinking about modifying log4j

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988510#comment-13988510 ] Ralph Goers commented on LOG4J2-628: I don't think using a fictional clock will work

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13988580#comment-13988580 ] Remko Popma commented on LOG4J2-628: I agree. Also, using the Clock interface for

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986881#comment-13986881 ] Bryan Hsueh commented on LOG4J2-628: Correct, my use case is not performance related.

Re: [jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

If we used Clock consistently throughout, does this make sense to use everywhere? We use the clock to determine thread killing timeouts for instance. There are other places time is used that if it were to use the Clock interface, we'd have to document the contract required to be followed by it in

Re: [jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

Matt, can you make this a Jira comment? Not sure Bryan is on this list I'd prefer to have the full discussion either in the Jira comments or on the list: half-half will be confusing... Sent from my iPhone On 2014/05/02, at 5:19, Matt Sicker boa...@gmail.com wrote: If we used Clock

Re: [jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

Actually, Matt, I take that back with apologies. I'll start a discussion thread on the dev list. The Jira can be focussed on the user requirements. On Fri, May 2, 2014 at 7:02 AM, Remko Popma remko.po...@gmail.com wrote: Matt, can you make this a Jira comment? Not sure Bryan is on this list

[jira] [Commented] (LOG4J2-628) Cannot set log4j.Clock with Async appender

[ https://issues.apache.org/jira/browse/LOG4J2-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13986246#comment-13986246 ] Remko Popma commented on LOG4J2-628: This is expected behaviour as of RC-1. The use