That depends on the environment. You could be getting the Logger from the wrong
LoggerContext.
Ralph
> On Apr 15, 2016, at 7:13 AM, Matt Sicker wrote:
>
> Couldn't he just cache the LoggerContext and use LoggerContext.getLogger()
> to avoid the ContextSelector lookup?
>
> On 15 April 2016 at
Couldn't he just cache the LoggerContext and use LoggerContext.getLogger()
to avoid the ContextSelector lookup?
On 15 April 2016 at 08:19, Ralph Goers wrote:
> The logging implementation stores the logger in a map. However, when you
> call getLogger ClassLoaderContextSelector will have to locat
The logging implementation stores the logger in a map. However, when you call
getLogger ClassLoaderContextSelector will have to locate the ClassLoader for
the class loading the Logger. This can be fairly expensive. If you are using a
different ContextSelector it might work better. Or you can cr
Hi,
I've got an application, where I would like to obtain loggers on the
fly, because the logger name isn't known in advance. (Think of it as a
logging server, which will be used by remote clients.)
Now, creating a Logger might be an expensive operation. Thus, my question:
- Would you recommend
