|
|
Steve Ikeoka created an issue |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.21.0 |
|
Assignee: |
|
|
Components: |
Main |
|
Created: |
27/May/22 9:52 PM |
|
Environment: |
WildFly application server |
|
Priority: |
|
|
Reporter: |
Medium|
There is a regression bug when deploying the GeoServer 2.21.0 WAR in a WildFly application server where the RELINQUISH_LOG4J_CONTROL setting is only partially working. Some GeoServer loggers will log properly according to the WildFly logging configuration while other GeoServer loggers will not log properly. This appears to be somehow related to the classloader loading log4j-core classes from org.geoserver.logging.LoggingUtils imports when attempting to set the value of the relinquishLog4jControl variable and refactoring LoggingUtils to eliminate any log4j-core imports fixed the problem for me. |
|
|
|
Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS |
|
|
This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100198-sha1:b34c10a) |
|
|
|
