Am 19.03.2017 um 05:50 schrieb Adam Gent:
I accidentally unsubscribed but I figured I would start a new thread
on what I mean by the Chicken/Egg configuration problem with SL4FJ.
The problem is you often in cloud environments want a fully resolved
configuration with out doing logging.
.... But you can't have fully correctly configured logging with out
configuration being complete.... but you can't a proper configuration
with out using logging.
I'm not talking about some reentrant or endless recursive calls or
infinite loop that the event queue in LogFactory prevents.
Lets go over this with a configuration initialization that is agnostic
of logging backend.
1. static main - initialization
2. configuration code begins
3. configuration needs to set some system properties and various
singletons required by a backend logging framework and various other
downstream libraries (the best way to configure old log4j is still
through system properties)
4. configuration code needs to get external configuration to set these
properties
5. configuration code uses a library that has SLF4J in it (lets say
Zookeeper but it could be any sort of configuration library like
Archaius).
5. SLF4J initialization begins
6. Backend logging initialization begins but is missing required
system properties and/or singletons.
How this?
Step 3 is supposed to provide all this.
7. Backend logging finishes initialization but is incorrect
8. Logging events do not have correct MDC attributes but worse Logging
appenders may not be setup correctly.
Since we disagree about what problems can happen, I'm leaving discussion
of the solutions to another thread.
(I do believe you that you did have problems, I just do not agree with
the problem description because it doesn't make sense to me - yet.)
_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user
