[logging-log4j2] branch master updated: Fix (more) broken links for LMAX Disruptor.

[vy...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

vy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git


The following commit(s) were added to refs/heads/master by this push:
     new 3919896  Fix (more) broken links for LMAX Disruptor.
3919896 is described below

commit 39198962ad9a4b23faf344cc85bc649192149e18
Author: Volkan Yazıcı <vo...@yazi.ci>
AuthorDate: Fri Nov 5 10:40:43 2021 +0100

    Fix (more) broken links for LMAX Disruptor.
---
 .../main/java/org/apache/logging/log4j/core/async/AsyncLogger.java | 4 ++--
 .../org/apache/logging/log4j/core/async/AsyncLoggerConfig.java     | 7 +++----
 src/site/asciidoc/performance.adoc                                 | 2 +-
 3 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLogger.java b/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLogger.java
index 36370ab..d8b1c45 100644
--- a/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLogger.java
+++ b/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLogger.java
@@ -48,8 +48,8 @@ import com.lmax.disruptor.dsl.Disruptor;
 /**
  * AsyncLogger is a logger designed for high throughput and low latency logging. It does not perform any I/O in the
  * calling (application) thread, but instead hands off the work to another thread as soon as possible. The actual
- * logging is performed in the background thread. It uses the LMAX Disruptor library for inter-thread communication. (<a
- * href="http://lmax-exchange.github.com/disruptor/" >http://lmax-exchange.github.com/disruptor/</a>)
+ * logging is performed in the background thread. It uses <a href="https://lmax-exchange.github.io/disruptor/">LMAX
+ * Disruptor</a> for inter-thread communication.
  * <p>
  * To use AsyncLogger, specify the System property
  * {@code -DLog4jContextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector} before you obtain a
diff --git a/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerConfig.java b/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerConfig.java
index 796f56d..6cfc40e 100644
--- a/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerConfig.java
+++ b/log4j-core/src/main/java/org/apache/logging/log4j/core/async/AsyncLoggerConfig.java
@@ -48,10 +48,9 @@ import org.apache.logging.log4j.util.Strings;
  * AsyncLoggerConfig is a logger designed for high throughput and low latency
  * logging. It does not perform any I/O in the calling (application) thread, but
  * instead hands off the work to another thread as soon as possible. The actual
- * logging is performed in the background thread. It uses the LMAX Disruptor
- * library for inter-thread communication. (<a
- * href="http://lmax-exchange.github.com/disruptor/"
- * >http://lmax-exchange.github.com/disruptor/</a>)
+ * logging is performed in the background thread. It uses
+ * <a href="https://lmax-exchange.github.io/disruptor/">LMAX Disruptor</a>
+ * for inter-thread communication.
  * <p>
  * To use AsyncLoggerConfig, specify {@code <asyncLogger>} or
  * {@code <asyncRoot>} in configuration.
diff --git a/src/site/asciidoc/performance.adoc b/src/site/asciidoc/performance.adoc
index 4e25ba5..c0bc955 100644
--- a/src/site/asciidoc/performance.adoc
+++ b/src/site/asciidoc/performance.adoc
@@ -126,7 +126,7 @@ business logic very quickly.
 
 It turns out that the choice of queue is extremely important for peak
 throughput. Log4j 2's Async Loggers use a
-http://lmax-exchange.github.com/disruptor/[lock-free data structure],
+https://lmax-exchange.github.io/disruptor/[lock-free data structure],
 whereas Logback, Log4j 1.2 and Log4j 2's Asynchronous Appenders use an
 ArrayBlockingQueue. With a blocking queue, multi-threaded applications
 often experience lock contention when trying to enqueue the log event.