Use Maven central for connect timeout tests. Accessing sling.apache.org failed with a 'connection refused' error on Jenkins, presumably since builds.apache.org has direct access to other apache.org servers.
diff --git a/src/test/java/org/apache/sling/uca/impl/IntegrationTest.java b/src/test/java/org/apache/sling/uca/impl/IntegrationTest.java
index 0a3af13..9e42394 100644
--- a/src/test/java/org/apache/sling/uca/impl/IntegrationTest.java
+++ b/src/test/java/org/apache/sling/uca/impl/IntegrationTest.java
@@ -48,7 +48,7 @@
* <p>It is surprisingly hard to simulate a connnection timeout. The most reliable way seems to
* be to get a firewall to drop packets, but this is very hard to do portably and safely
* in a unit test. The least bad possible solution is to access an URL that we know will timeout
- * and that is related to us - the Sling website.</p>
+ * and that is able to sustain additional traffic. Maven Central is a good candidate for that.</p>
*
* @throws IOException various I/O problems
*/
@@ -56,7 +56,7 @@
public void connectTimeout() throws IOException {
SocketTimeoutException exception = assertThrows(SocketTimeoutException.class,
- () -> assertTimeout(ofSeconds(5), () -> runTest("http://sling.apache.org:81"))
+ () -> assertTimeout(ofSeconds(5), () -> runTest("http://repo1.maven.org:81"))
);
assertEquals("connect timed out", exception.getMessage());
}
