[
https://issues.jboss.org/browse/WFLY-6775?page=com.atlassian.jira.plugin....
]
James Perkins updated WFLY-6775:
--------------------------------
Summary: Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.22 (was: Upgrade slf4j
from version 1.7.7.jbossorg-1 to 1.7.21)
Upgrade slf4j from version 1.7.7.jbossorg-1 to 1.7.22
-----------------------------------------------------
Key: WFLY-6775
URL:
https://issues.jboss.org/browse/WFLY-6775
Project: WildFly
Issue Type: Component Upgrade
Components: Logging
Reporter: James Perkins
Assignee: James Perkins
Note both WildFly and WildFly Core will need to be updated. It may be possible to remove
the dependencies from WildFly and keep everything in core. However it needs to be
determined if we should add all the slf4j dependencies to core.
There should no longer be a need for the forked version. The fix for
[SLF4J-167|http://jira.qos.ch/browse/SLF4J-167] should be in version 1.7.14 with some
additional fixes for replaying the previously lost logs.
[Quote from comment on
JIRA|http://jira.qos.ch/browse/SLF4J-167?focusedCommentId=17048&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17048]
{quote}
The problem of lost logs during initialization in a multi-threaded application is solved
by storing and replaying the logs which would be otherwise lost. Fix available in SLF4J
version 1.7.15.
{quote}
Analysis will need to be done to ensure this works as expected before the fork is no
longer required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)