January 2018 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1368) logback-classic LogbackServletContainerInitializer class initialize logger context before setting logback.configurationFile
by QOS.CH (JIRA) 08 Jan '18

08 Jan '18

pegah created LOGBACK-1368: ------------------------------ Summary: logback-classic LogbackServletContainerInitializer class initialize logger context before setting logback.configurationFile Key: LOGBACK-1368 URL: https://jira.qos.ch/browse/LOGBACK-1368 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.3, 1.1.11, 1.2.2, 1.2.0, 1.1.10 Reporter: pegah Assignee: Logback dev list In logback-classic in version later than 1.1.9, an enhancement was implemented according to issue LOGBACK-1170 that in web-applications it automatically install a listener. and during this installation it initialize a logger context while the logback.configurationFile property is not set yet. Since logger context is single tone we can not reinitialize it again. There should be some way to set this property before initialization. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1367) Docs: Are there outdated APIs (e.g., WriterAppender) in the site?
by QOS.CH (JIRA) 06 Jan '18

06 Jan '18

Seonah created LOGBACK-1367: ------------------------------- Summary: Docs: Are there outdated APIs (e.g., WriterAppender) in the site? Key: LOGBACK-1367 URL: https://jira.qos.ch/browse/LOGBACK-1367 Project: logback Issue Type: Bug Components: logback-site Affects Versions: 1.2.3 Reporter: Seonah Assignee: Logback dev list Priority: Minor I am checking the APIs in the Logback site, and I found outdated APIs. I hope some contributors may confirm whether the followings are outdated or not: 1. "WriterAppender" has been deleted. However, two html pages still include it. https://github.com/qos-ch/logback/blob/master/logback-site/src/site/pages/c… https://github.com/qos-ch/logback/blob/master/logback-site/src/site/pages/d… 2. "SocketAppenderBase", "JMSQueueAppender", "JMSTopicAppender" have been deleted. However, the below html page still includes them. https://github.com/qos-ch/logback/blob/master/logback-site/src/site/pages/d… Thanks in advance, Seonah -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1027) Circular Referenced Suppressed Exception Throws StackOverflowError
by QOS.CH (JIRA) 05 Jan '18

05 Jan '18

1 0

[JIRA] (LOGBACK-1366) ConcurrentModificationException when calling Logger.detachAndStopAllAppenders
by QOS.CH (JIRA) 04 Jan '18

04 Jan '18

Kenneth Gendron created LOGBACK-1366: ---------------------------------------- Summary: ConcurrentModificationException when calling Logger.detachAndStopAllAppenders Key: LOGBACK-1366 URL: https://jira.qos.ch/browse/LOGBACK-1366 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Reporter: Kenneth Gendron Assignee: Logback dev list When attempting to detach and stop all appenders (specifically SiftingAppender) associated with a logger, logback may throw a ConcurrentModificationException if another thread is currently logging. {{java.util.ConcurrentModificationException: null}} {{ at java.util.LinkedHashMap$LinkedHashIterator.nextNode(LinkedHashMap.java:719)}} {{ at java.util.LinkedHashMap$LinkedValueIterator.next(LinkedHashMap.java:747)}} {{ at ch.qos.logback.core.spi.AbstractComponentTracker.allComponents(AbstractComponentTracker.java:234)}} {{ at ch.qos.logback.core.sift.SiftingAppenderBase.stop(SiftingAppenderBase.java:89)}} {{ at ch.qos.logback.core.spi.AppenderAttachableImpl.detachAndStopAllAppenders(AppenderAttachableImpl.java:107)}} {{ at ch.qos.logback.classic.Logger.detachAndStopAllAppenders(Logger.java:206)}} {{ at automation.config.logging.LoggerGenerator.destroyLogger(LoggerGenerator.java:143)}} {{ at processflow.ProcessHandler.destroyProcessContext(ProcessHandler.java:862)}} {{ at automation.config.processflow.ProcessContextHandler.processConnection(ProcessContextHandler.java:636)}} {{ at automation.config.processflow.DatabaseService$Processor.processConnection(DatabaseService.java:281)}} {{ at appserversupport.sql.ConnectionProcessor$Processor.run(ConnectionProcessor.java:187)}} {{ at java.lang.Thread.run(Thread.java:745)}} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1365) Fix documentation how to submit doc improvements
by QOS.CH (JIRA) 04 Jan '18

04 Jan '18

Simon created LOGBACK-1365: ------------------------------ Summary: Fix documentation how to submit doc improvements Key: LOGBACK-1365 URL: https://jira.qos.ch/browse/LOGBACK-1365 Project: logback Issue Type: Bug Components: logback-site Environment: I followed the text {quote}We are actively looking for volunteers to proofread the documentation. Please send your corrections or suggestions for improvement to "corrections(a)qos.ch". {quote} But was redirected (via email) to submit a JIRA issue. So the text should be fixed. [My PR|https://github.com/qos-ch/logback/pull/372] from 2017-04-28 might be incorrect, since PRs without JIRA tickets seem to be ignored. Reporter: Simon Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1364) MDC.setContextMap documentation
by QOS.CH (JIRA) 04 Jan '18

04 Jan '18

Simon created LOGBACK-1364: ------------------------------ Summary: MDC.setContextMap documentation Key: LOGBACK-1364 URL: https://jira.qos.ch/browse/LOGBACK-1364 Project: logback Issue Type: Bug Components: logback-site Environment: The documentation refers to {{MDC.setContextMapValues}}, but the function is called {{MDC.setContextMap}}. PR submitted on 2017-04-28: https://github.com/qos-ch/logback/pull/372 Reporter: Simon Assignee: Logback dev list -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1363) [logback-access] Response header field names to be case-insensitive
by QOS.CH (JIRA) 03 Jan '18

03 Jan '18

1 0

[JIRA] (LOGBACK-1363) [logback-access] Response header field names to be case-insensitive
by QOS.CH (JIRA) 03 Jan '18

03 Jan '18

Nathan Schile created LOGBACK-1363: -------------------------------------- Summary: [logback-access] Response header field names to be case-insensitive Key: LOGBACK-1363 URL: https://jira.qos.ch/browse/LOGBACK-1363 Project: logback Issue Type: Improvement Components: logback-access Affects Versions: 1.2.3 Environment: Jetty 9.4, Linux, Java 8 Reporter: Nathan Schile Assignee: Logback dev list Priority: Minor Response header lookup provided by the AccessEvent are case-sensitive. The RFC for message headers says that the header names should be treated as case-insensitive [1]. Request headers are already treated as case-insensitive [2]. Response header lookup should be updated to be case-insensitive. [1] https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2 [2] https://github.com/qos-ch/logback/blob/v_1.2.3/logback-access/src/main/java… -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

How to add a IP Whitelist to ServerSocketReceiver
by Blum, Ori 02 Jan '18

02 Jan '18

I have a project to convert Log4j to Logback/SLF4j. I log4j I wrote a logging socket server a server that enforces an IP whitelist. The server only accepts a socket connection from an IP in the list. I am attempting, not successfully, to recreate the same attempting to extend the server listener. The issue is all the classes are package scope. Has anyone managed to create a Socket Server that restricts client connections? The information contained in this e-mail, and any attachment, is confidential and is intended solely for the use of the intended recipient. Access, copying or re-use of the e-mail or any attachment, or any information contained therein, by any other person is not authorized. If you are not the intended recipient please return the e-mail to the sender and delete it from your computer. Although we attempt to sweep e-mail and attachments for viruses, we do not guarantee that either are virus-free and accept no liability for any damage sustained as a result of viruses. Please refer to http://disclaimer.bnymellon.com/eu.htm for certain disclosures relating to European legal entities.

1 0