From 97661c8c13675f5532043f36a200b6c4c4f70d15 Mon Sep 17 00:00:00 2001
From: April M <36110273+aimurphy@users.noreply.github.com>
Date: Tue, 21 Oct 2025 07:45:03 -0700
Subject: [PATCH] java driver link

---
 modules/ROOT/pages/troubleshooting-scenarios.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/troubleshooting-scenarios.adoc b/modules/ROOT/pages/troubleshooting-scenarios.adoc
index 6b68f9f2..fc595ddf 100644
--- a/modules/ROOT/pages/troubleshooting-scenarios.adoc
+++ b/modules/ROOT/pages/troubleshooting-scenarios.adoc
@@ -60,7 +60,7 @@ V4 is a good recommendation that usually fits all but if the user is migrating f
 
 To force the protocol version on the Java driver, see the documentation for your version of the Java driver:
 
-* https://github.com/apache/cassandra-java-driver/tree/4.x/manual/core/native_protocol[{cass-reg} Java driver 4.18 and later: Controlling the protocol version]
+* https://apache.github.io/cassandra-java-driver/4.19.0/core/native_protocol/?h=controlling#controlling-the-protocol-version[{cass-reg} Java driver 4.18 and later: Controlling the protocol version]
 * https://docs.datastax.com/en/developer/java-driver/latest/manual/core/native_protocol/index.html#controlling-the-protocol-version[{company} Java driver 4.17 and earlier: Controlling the protocol version]
 
 == Protocol errors in the proxy logs but clients can connect successfully