Did you include the LMAX disruptor dependency? That's required for async
loggers.
On 15 April 2014 08:10, David KOCH wrote:
> Hello,
>
> Glassfish 3.1.2 does not seem to find (some) log4j2 classes when the log4j2
> dependencies are not directly included in the wep application's pom.xml. In
> my
Hello,
Glassfish 3.1.2 does not seem to find (some) log4j2 classes when the log4j2
dependencies are not directly included in the wep application's pom.xml. In
my case, I have a separate artifact which contains a custom log appender
and all of the log4j2 stuff.
I already followed the advice in
LPS
