title: How to verify log4j2 is logging asynchronously via LMAX disruptor?
body: <p>I am developing an Eclipse RCP application and have gone to some pains to get log4j2 to work within the app. All seems to work fine now, and as a finishing touch I wanted to make <a href="https://logging.apache.org/log4j/2.x/manual/async.html#AllAsync" rel="noreferrer">all loggers asynchronously</a>. </p>
  
  <p>I've managed to get the LMAX Disruptor on the classpath, and think I've solved the <a href="https://stackoverflow.com/q/32628098/731040">issue</a> of providing <code>sun.misc</code> as well. Set the VM argument <code>-DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector</code> in the run config and set up <em>log4j2.xml</em> file correctly as well. <strong>I think</strong>. And that's where the problem is. I'd like to be able to verify that my application logs asynchronously in the proper fashion, so I can enjoy the benefits latency-wise.</p>
  
  <p>How can I - then - verify that my loggers are working asynchronously, utilising the LMAX Dirsuptor in the process?</p>