If you use pax-logging-log4j2, you can migrate easily, though the version of log4j2 in there is somewhat out of date.
Async appender will certainly alleviate some issues, but it can't do much about APIs that publicly add the synchronized keyword to hot spots like in log4j1. On 7 November 2017 at 11:53, Andrei Shakirin <[email protected]> wrote: > Hi Matt, > > Thanks for quick response, but I don't use log4j directly, only through > the pax-logging-service.jar. > And the issue is still there even with last released pax-logging-service > version (1.10.1). > > Async appender is an option, will definitely try that. > > Regards, > Andrei. > > -- > -- > ------------------ > OPS4J - http://www.ops4j.org - [email protected] > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Matt Sicker <[email protected]> -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
