Did you include the LMAX disruptor dependency? That's required for async
loggers.


On 15 April 2014 08:10, David KOCH <dk...@ezakus.com> 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 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-21525<https://issues.liferay.com/browse/LPS-21525> to
> help avoid some errors but I still get the following messages when trying
> to deploy my application,
>
>
> [#|2014-04-15T14:24:15.933+0200|WARNING|glassfish3.1.2|org.glassfish.weld.BeanDeploymentArchiveImpl|_ThreadID=21;_ThreadName=Thread-3;|Error
> while trying to load Bean Class
> org.apache.logging.log4j.core.async.RingBufferLogEvent$Factory :
> java.lang.NoClassDefFoundError: com/lmax/disruptor/EventFactory|#]
>
> See here <http://pastebin.com/RWRH2uxm> for a verbose list.
>
> The classes are present in the web application's jar, albeit in:
>
> WEB-INF/lib/<my_jar_with_log4j2_and_customer_appender>/org/..../*<log4j2_related>.class.
>
> How can I fix this? Any help is appreciated,
>
> Regards,
>
> /David
>



-- 
Matt Sicker <boa...@gmail.com>

Reply via email to