I'm trying to get a solution to https://jira.qos.ch/browse/LOGBACK-1189, in which async logging for logback-access with Jetty incorrectly clears the attribute map due to bad logic in copyAttributeMap. I've proposed https://github.com/qos-ch/logback/pull/336 as a resolution to the problem. Would greatly appreciate some feedback on if this proposed change will be accepted, and if so, when it might be released, and if not, when we might expect a fix for LOGBACK-1189, which is affecting a number of projects, including Dropwizard: http://mailman.qos.ch/pipermail/logback-user/2016-September/004800.html Thanks.