Please see https://issues.apache.org/jira/browse/LOG4J2-732
Mariano, please checkout and build trunk and see if you like using the LMAX Disruptor 3.3.0 :-) This update required no code changes. Feel free to close the ticket if your case runs OK. Gary On Tue, Jul 22, 2014 at 5:56 PM, Remko Popma <[email protected]> wrote: > Mariano, the site says async loggers require 3.0.0 or higher. So they'll > work with 3.0 and better. We've tested with 3.0. 3.1, 3.2 and 3.2.1. > > We haven't tested with 3.3 yet. > > Gary, the Disruptor 3.3 release notes mention a breaking api change, so > let's keep it at 3.2.1 until I've had a chance to look at it. > > Sent from my iPhone > > > On 2014/07/23, at 3:13, Gary Gregory <[email protected]> wrote: > > > > It looks like 3.3.0 is the latest. > > > > Feel free to submit a patch. > > > > Gary > > > > <div>-------- Original message --------</div><div>From: Mariano Gonzalez > <[email protected]> </div><div>Date:07/22/2014 11:18 > (GMT-05:00) </div><div>To: Log4J Users List < > [email protected]> </div><div>Subject: Disruptor 3.2.x > </div><div> > > </div>Hello, > > > > According to the manual, async loggers require Disruptor 3.0. However, > the > > 3.2.x series of disruptor is available. Have you tried this version? Are > > you recommending 3.0 because you found issues with other versions or is > it > > just in your TODO list to give 3.2 a ride and/or update the manual? > > > > Thanks > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- E-Mail: [email protected] | [email protected] Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
