From e645d046a870d37c958232f45c3c409beae2a2ff Mon Sep 17 00:00:00 2001 From: Matthias Stock Date: Thu, 19 May 2022 17:13:04 +0200 Subject: [PATCH] Removed dead link from jdbc.adoc The linked resource is not available anymore: https://web.archive.org/web/20210228160648/https://blog.engineyard.com/5-subtle-ways-youre-using-mysql-as-a-queue-and-why-itll-bite-you --- src/reference/asciidoc/jdbc.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/reference/asciidoc/jdbc.adoc b/src/reference/asciidoc/jdbc.adoc index dd3f0bae51..14fd5ce295 100644 --- a/src/reference/asciidoc/jdbc.adoc +++ b/src/reference/asciidoc/jdbc.adoc @@ -477,9 +477,8 @@ public class JsonPreparedStatementSetter extends ChannelMessageStorePreparedStat ==== Generally, we do not recommend using a relational database for queuing. Instead, if possible, consider using either JMS- or AMQP-backed channels instead. -For further reference, see the following resources: +For further reference, see the following resource: -* https://www.engineyard.com/blog/2011/5-subtle-ways-youre-using-mysql-as-a-queue-and-why-itll-bite-you/[5 subtle ways you’re using MySQL as a queue, and why it’ll bite you]. * https://mikehadlow.blogspot.com/2012/04/database-as-queue-anti-pattern.html[The Database As Queue Anti-Pattern]. ====