The following error is sometimes logged during the EAP startup, version EAP 6.2.0.ER3: 02:56:13,466 ERROR [stderr] (MSC service thread 1-3) SLF4J: The following loggers will not work because they were created 02:56:13,468 ERROR [stderr] (MSC service thread 1-3) SLF4J: during the default configuration phase of the underlying logging system. 02:56:13,469 ERROR [stderr] (MSC service thread 1-3) SLF4J: See also http://www.slf4j.org/codes.html#substituteLogger 02:56:13,476 ERROR [stderr] (MSC service thread 1-3) SLF4J: org.apache.ws.security.WSSConfig See the startup log here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-manu-acceptance-startup-RHEL-dev/13/jdk=java16_default,label=RHEL6_x86_64/artifact/target/manu-reports/units/manu.testsuite.eap6.acceptance.startup.CleanStartupAcceptanceEap6/jboss-eap-6.2/domain/server-one/server.log Seen on RHEL, solaris, windows.
Is this by chance reproducible? I can't seem to get the message to appear.
This was seen on ER4 build as well. Reproducible: around 40% of all clean startups of EAP have this error in logs. Just unzip EAP, start domain and observe the error. Or start two EAP's with standalone-ha or standalone-full-ha, ... profile on one machine with different ports.
The issue affects also RPM based installations. Clean start/stop is one of the requirements for release, thus proposing this as blocker.
This looks like an slf4j-api bug. I'm forking the repo on GitHub and doing up a patch for it.
This would be the proposed patch for slf4j https://github.com/jamezp/slf4j/compare/issue176.
Adding the slf4j issue http://bugzilla.slf4j.org/show_bug.cgi?id=176
This requires a fix in slf4j. The issue linked above was opened in 2010 and doesn't seem to have much movement on it. The patch I've linked to this issue and attached to the slf4j issue should work. If someone wants to maintain a fork of slf4j, then that should fix this issue.
Based on the error in the server.log (and posted in #c1), all log messages from org.apache.ws.security.WSSConfig will be lost for the life of the JVM since that logger member is static: 54 public class WSSConfig { 55 56 private static final org.apache.commons.logging.Log LOG = 57 org.apache.commons.logging.LogFactory.getLog(WSSConfig.class); Do we know how many classes this could potentially affect? It seems pretty risky to me to have potentially any component that uses SLF4J or Apache Commons Logging to lose its logging messages if it's initialized at a certain time. This issue may have existed already, but with the increased visibility to our customers, this will likely make some of them uneasy and file a support case and maybe even request a patch for it.
James Perkins <jperkins> made a comment on jira WFLY-2425 Pull request merged
This issue was verified using the 6.2.0.CR1 preview bits.