[wildfly-dev] Logging Changes

[Brian Stansberry]

On Thu, Dec 7, 2017 at 5:46 PM, David Lloyd <david.lloyd at redhat.com> wrote:

> On Thu, Dec 7, 2017 at 2:02 PM, James Perkins <jperkins at redhat.com> wrote:
> > There will be a slight performance impact during boot. This can be
> greatly
> > reduced if the caller calculation is disabled. This can be done in normal
> > cases, but we likely can't make it the default.
>
> I suspect we can safely disable caller calculation by default on boot,
> as long as users have an easy way to turn it on.
>
> Also I think we should consider some kind of grimy hack to bootstrap
> the logging subsystem first, if it's present, otherwise immediately
> fall back to properties-based config if it's absent.
>
> I'm not sure what counts as first in this context, but fwiw if a logging
subsystem is present during boot we always execute it's Stage.RUNTIME steps
first before proceeding on to doing the parallel execution of the other
subsystems. We could probably without too much trouble get a bit more
grimy, e.g. to get the subsystem ops to run before a few others if they
don't already. Beyond that I sense we wouldn't be talking grimy, we'd be
talking horrible. :)

--
> - DML
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>



-- 
Brian Stansberry
Manager, Senior Principal Software Engineer
Red Hat
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20171212/094f0f26/attachment.html