[wildfly-dev] Logging Changes
David Lloyd
david.lloyd at redhat.com
Tue Dec 12 14:11:48 EST 2017
On Tue, Dec 12, 2017 at 11:37 AM, Brian Stansberry
<brian.stansberry at redhat.com> wrote:
> 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.
OK, that's exactly what I was alluding to, and we already do it, so
it's all fine then.
--
- DML
More information about the wildfly-dev
mailing list