From 51969fd1961b1dcaa7a2e12cdf86ebdb35314e85 Mon Sep 17 00:00:00 2001 From: Gary Gregory Date: Thu, 14 Nov 2024 07:50:01 -0500 Subject: [PATCH] Provide a more helpful TimeoutException message - One cannot tell what endpoint is at fault in a non-trivial configuration, for example, using an AsyncMiddleManServlet, is it the origin or the client? - The TimeoutException message now contains the endpoint causing the timeout --- .../src/main/java/org/eclipse/jetty/io/IdleTimeout.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jetty-core/jetty-io/src/main/java/org/eclipse/jetty/io/IdleTimeout.java b/jetty-core/jetty-io/src/main/java/org/eclipse/jetty/io/IdleTimeout.java index 71c07b352a5..94cd3d35b87 100644 --- a/jetty-core/jetty-io/src/main/java/org/eclipse/jetty/io/IdleTimeout.java +++ b/jetty-core/jetty-io/src/main/java/org/eclipse/jetty/io/IdleTimeout.java @@ -164,7 +164,7 @@ public abstract class IdleTimeout { if (idleLeft <= 0) { - TimeoutException timeout = new TimeoutException("Idle timeout expired: " + idleElapsed + "/" + idleTimeout + " ms"); + TimeoutException timeout = new TimeoutException("Idle timeout expired: " + idleElapsed + "/" + idleTimeout + " ms in " + this); if (LOG.isDebugEnabled()) LOG.debug("{} idle timeout expired", this, timeout); try