Re: Are we using spin loops anywhere?

I don't think we use spin locks in production code anywhere. The latency test has a wait strategy interface and one of the implementations is spinning. I need to check the comments but not sure if I used that strategy for the latency tests for the garbage free performance page. Sent from my i

Are we using spin loops anywhere?

I thought we were using it in AppenderControlArraySet for example, but it doesn't look like it really matches the idea. I've been reading through all the JEPs in JDK9 to see if there's anything else useful we haven't already marked in our epic , an

[jira] [Closed] (LOG4J2-1743) CompositeConfiguration does not add filters to appenderRefs

[ https://issues.apache.org/jira/browse/LOG4J2-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toby Shepheard closed LOG4J2-1743. -- Thanks > CompositeConfiguration does not add filters to appenderRefs > ---

Jenkins build is back to stable : Log4j 2.x #2546

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

[jira] [Commented] (LOG4J2-1521) StringIndexOutOfBoundsException thrown when rolling logs

[ https://issues.apache.org/jira/browse/LOG4J2-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15756659#comment-15756659 ] Remko Popma commented on LOG4J2-1521: - We have recently updated the FastDateFormat-re

[jira] [Updated] (LOG4J2-1191) Log4j completely hangs in TcpSocketManager after a while...

[ https://issues.apache.org/jira/browse/LOG4J2-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1191: Priority: Major (was: Blocker) > Log4j completely hangs in TcpSocketManager after a while... > ---

[jira] [Updated] (LOG4J2-1686) Support conditional configuration

[ https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1686: Priority: Major (was: Blocker) > Support conditional configuration > -

[jira] [Updated] (LOG4J2-1640) RollingFileAppender with CronTriggeringPolicy broken?

[ https://issues.apache.org/jira/browse/LOG4J2-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma updated LOG4J2-1640: Priority: Major (was: Blocker) > RollingFileAppender with CronTriggeringPolicy broken? > -

[jira] [Closed] (LOG4J2-1744) Custom logger Generate tool should not require log4j-api dependency

[ https://issues.apache.org/jira/browse/LOG4J2-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma closed LOG4J2-1744. --- Resolution: Fixed Fixed in commit e40dc2b. > Custom logger Generate tool should not require log4j-ap

[jira] [Resolved] (LOG4J2-1302) log4j-slf4j-impl should provide a runtime dependency on log4j-core

[ https://issues.apache.org/jira/browse/LOG4J2-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Remko Popma resolved LOG4J2-1302. - Resolution: Fixed Fix Version/s: 2.8 Fixed in commit 86751f4. Please verify and close. >

[jira] [Created] (LOG4J2-1744) Custom logger Generate tool should not require log4j-api dependency

Remko Popma created LOG4J2-1744: --- Summary: Custom logger Generate tool should not require log4j-api dependency Key: LOG4J2-1744 URL: https://issues.apache.org/jira/browse/LOG4J2-1744 Project: Log4j 2