-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
None
There is already a way to lock/protect configuring loggers, handlers, formatters and filters. However, this doesn't really work in environments like WildFly where deployments may break this. It would be useful to have a way to print a warning if configuration was attempted outside of something like the logging subsystem in WildFly. A simple object would be used to indicate the configurator has access to configure the log manager.
- blocks
-
JBEAP-21296 [GSS](7.4.z) WFCORE-5275 - Socket handler prevents server from starting
- Closed
-
JBEAP-21291 [GSS](7.4.z) WFCORE-4910 - Log WARN if JBoss Logging Handler gets removed
- New
-
WFCORE-4910 Log WARN if JBoss Logging Handler gets removed
- Reopened
- is related to
-
WFCORE-5275 Socket handler is holding server to start
- Open