You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by vy...@apache.org on 2021/11/05 09:35:08 UTC
[logging-log4j2] branch release-2.x updated: Fix broken links to
LMAX Disruptor.
This is an automated email from the ASF dual-hosted git repository.
vy pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
The following commit(s) were added to refs/heads/release-2.x by this push:
new 35b89fe Fix broken links to LMAX Disruptor.
35b89fe is described below
commit 35b89fe5c73f55dc154a1a049e991a6e9890997c
Author: Volkan Yazici <vo...@yazi.ci>
AuthorDate: Fri Nov 5 10:35:25 2021 +0100
Fix broken links to LMAX Disruptor.
---
.../main/java/org/apache/logging/log4j/core/async/AsyncLogger.java | 4 ++--
.../org/apache/logging/log4j/core/async/AsyncLoggerConfig.java | 7 +++----
src/site/xdoc/manual/async.xml | 2 +-
src/site/xdoc/performance.xml | 2 +-
src/site/xdoc/runtime-dependencies.xml | 2 +-
5 files changed, 8 insertions(+), 9 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 6b0b5d7..9d48c8a 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 33beab3..f8d4102 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/xdoc/manual/async.xml b/src/site/xdoc/manual/async.xml
index e704f78..c30cd30 100644
--- a/src/site/xdoc/manual/async.xml
+++ b/src/site/xdoc/manual/async.xml
@@ -917,7 +917,7 @@ or
<subsection name="Under The Hood">
<p>
Asynchronous Loggers are implemented using the
- <a href="http://lmax-exchange.github.com/disruptor/">LMAX Disruptor</a>
+ <a href="https://lmax-exchange.github.io/disruptor/">LMAX Disruptor</a>
inter-thread messaging library. From the LMAX web site:
</p>
<blockquote>
diff --git a/src/site/xdoc/performance.xml b/src/site/xdoc/performance.xml
index ff892fa..a97a68a 100644
--- a/src/site/xdoc/performance.xml
+++ b/src/site/xdoc/performance.xml
@@ -121,7 +121,7 @@
</p>
<p>It turns out that the choice of queue is extremely important for peak throughput.
Log4j 2's Async Loggers use a
- <a href="http://lmax-exchange.github.com/disruptor/">lock-free data structure</a>, whereas
+ <a href="https://lmax-exchange.github.io/disruptor/">lock-free data structure</a>, 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.
diff --git a/src/site/xdoc/runtime-dependencies.xml b/src/site/xdoc/runtime-dependencies.xml
index 5ce30ff..6945832 100644
--- a/src/site/xdoc/runtime-dependencies.xml
+++ b/src/site/xdoc/runtime-dependencies.xml
@@ -236,7 +236,7 @@
</tr>
<tr>
<td>Async Loggers</td>
- <td><a href="http://lmax-exchange.github.io/disruptor/">LMAX Disruptor</a></td>
+ <td><a href="https://lmax-exchange.github.io/disruptor/">LMAX Disruptor</a></td>
</tr>
<tr>
<td>Kafka Appender</td>