Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Not recovering from SocketTimeoutException
  • From: Sai Sankar Challa <saisankar.c@xxxxxxxxxxxxxxxx>
  • Date: Mon, 14 Jun 2021 18:06:42 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=motivitylabs.com; dmarc=pass action=none header.from=motivitylabs.com; dkim=pass header.d=motivitylabs.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yqbcH94kKbjpNud/LAyfK8YDRQ1WBtIZjHomCx5KaYQ=; b=GEfbDtmE4Oo1/zZYJ9+gc9IO2fCXS2o8rE5tx9NwLqFB395cjzKfsN3KK0TMQ+8djAbeBQHgVCyqLtTRUmZqo5sWjJ56pD5yBupIF1Be5nm8YrnhoQyOtT+I7yoTIHPHA1k2JrRAKtkmyCFNjrvhgRx8MvLOkslW1aZ0oQhO8GEQkv4WLWlL0oXSJFJ5MGy/uSI6z2qVGIeauH4iZYdAnknoV9j6QedngtiqknGZZoaLw/LLTenoZVMpE3xQHzZUKiJRg2f0sJLlAsSsUAuwsql5dY7/NQZ7ZYB9KZDGlZGrfyxdumc4c2fnAyX4eDP/3MJLJv2Fz1dFWf1weJPP/g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ccwHcELtOyghahMh2pK4Z9SQBQh3md0KeADy0/d5NtE9qu7VAwJdNM7ww6jrpGBx9QsdRiy7TGjfDdFb9Pm468oWPSKf97LPoHwtQV8g1kqCi+ED9JBRfjhmesK8LC9Uf6gktrz3HDL+yPa8L62cZQOV7G+kDdCCeNlojth+f1VGH4+OsBFi99PbKQ1mfzke4oq9PNMasrFkJLGGI3ILgDNbFYCjMu2xvJSLNdJBOK5+vDVbZZlxzxDFz5CHZ39klsvGuLx/vasUjl1r36BC0nX7ozJbJatqhlf9IbwM7bnJM+TJmMyy7bIGsz8P3MJFnHSZ6RGLg1wbO/jf+fwTdg==
  • Delivered-to: jetty-users@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/jetty-users/>
  • List-help: <mailto:jetty-users-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/jetty-users>, <mailto:jetty-users-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AddT1Q5+e7eQ6NE4RjmmRInhqnNLrQBZAgGAAwOoiGA=
  • Thread-topic: [jetty-users] Not recovering from SocketTimeoutException
Thanks for the response.

What application ideally needs to do when it gets SocketTimeoutException from jetty layer, Please suggest.

Thanks in advance
Sai Sankar Challa

-----Original Message-----
From: Simone Bordet <sbordet@xxxxxxxxxxx> 
Sent: Sunday, May 30, 2021 3:20 PM
To: JETTY user mailing list <jetty-users@xxxxxxxxxxx>
Cc: Sai Sankar Challa <saisankar.c@xxxxxxxxxxxxxxxx>
Subject: Re: [jetty-users] Not recovering from SocketTimeoutException

Hi,

On Fri, May 28, 2021 at 5:23 PM Sai Sankar Challa via jetty-users <jetty-users@xxxxxxxxxxx> wrote:
>
> Hi Team
>
> Our customer in their environment getting SocketTimeoutException while Connecting to their exchange Urls with Jetty Clients.
>
> Once after started receiving this exception unless we restarted the node, this is not recovered. Customer is expecting not to restart explicitly rather need to handle this exception.
>
> Here is stack trace.
>
> java.net.SocketTimeoutException: Connect Timeout at 
> org.eclipse.jetty.io.ManagedSelector$Connect.run(ManagedSelector.java:
> 812) ~[?:?] at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511
> ) ~[?:1.8.0_232] at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> ~[?:1.8.0_232] at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.a
> ccess$201(ScheduledThreadPoolExecutor.java:180) ~[?:1.8.0_232] at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.r
> un(ScheduledThreadPoolExecutor.java:293) ~[?:1.8.0_232] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j
> ava:1149) ~[?:1.8.0_232] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> java:624) ~[?:1.8.0_232] at java.lang.Thread.run(Thread.java:748) 
> [?:1.8.0_232]
>
> Jetty version is : 9.4.22.v20191022
>
> Any pointers or help to handle this exception without restarting the node is highly appreciated.

If there is a connect timeout, it means that the server is not accepting connections in a timely fashion -- there is nothing that the client can do about this.

The SocketTimeoutException is reported to the HttpClient listeners, so the application code could be aware of the connect timeout.

This issue seems more an application/system problem, rather than something related to Jetty.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support from the Jetty & CometD experts.

Back to the top