Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qzF1y-00Euj9-JQ for pgsql-jdbc@arkaria.postgresql.org; Sat, 04 Nov 2023 11:41:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qzF1v-005gaV-M5 for pgsql-jdbc@arkaria.postgresql.org; Sat, 04 Nov 2023 11:41:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qzF1v-005gaN-CV for pgsql-jdbc@lists.postgresql.org; Sat, 04 Nov 2023 11:41:31 +0000 Received: from mail-pj1-x1030.google.com ([2607:f8b0:4864:20::1030]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qzF1s-004euh-FN for pgsql-jdbc@lists.postgresql.org; Sat, 04 Nov 2023 11:41:30 +0000 Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-2800bb246ceso2386721a91.1 for ; Sat, 04 Nov 2023 04:41:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699098086; x=1699702886; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ktaw0Zkui3Es190gCq8I9SV7WWoQM9dIFqvH72KtWbw=; b=e//LFn6nhBu0cMKuRCmE4bnyOWGEF1K+xi0yOUrbMBSt/t6xBETGC0+gn748X/HYaY +DSMWFa8BqDbiVfsxL0YK2/huS9iNsJESrgEAYbO2yGHQU1/hak+A10OvtUqWgikCXIZ Z9zdzQHIUBeGINR4S4kYKLzgmj8Oh3KavWd7SWar96uUv4QGB362moT0D+jXPx54A/3T JFR6Nzesuk9Zo7qfcoCfhgb/WaI4Pq4gbo3YXJl3H64yJx9xkMNgJaXhqAqEnzbgeFuf e+KyUkUZiP5dCngfgvgHM1g1LWM4P5uktqjfVU5Z6CIlZcjI83x/Bxfi51TgcsakRgMZ IfOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699098086; x=1699702886; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ktaw0Zkui3Es190gCq8I9SV7WWoQM9dIFqvH72KtWbw=; b=ulfXy6SFIF94TEokSPTXAC3gupFrF8k0H2EmTIHy1oPQLsVboJfUvJ/dIsXfL9xSV7 pYujeu/68uLtM4KFRGxqk6VndsIUXpXLj7unvsPSBHLYcm6qd1//Dp2/QFNRaMNguyC7 7XBB+hyGttMo9G6Scg4TZLuCdxwJsF1PlrOtKrJSBkMXPn+bl9i1Bw/XIR0VeNYRtXhK leSUWSOxf9IUDsSPOUFJPqdi9zZdo29uwW21tevwRbrKgmCyGrRVfba8uSLrZ5/3innA Jw2Tt1tB8s6L8Oq5q6R1ZmlGupVetjQ+OKai9cKdg/pki/tw6gwEeQMIJUEiM7VTj6BX Iamw== X-Gm-Message-State: AOJu0Ywz5JCb+ewF4mH/81AuTTxZfwIJkkkT2WNI7tLUrKgfQWRTqKVT LXeKTQZ2sZW/lXj5KhDA3Izv7IB//iZ8FRIPa7QYIdNEf1ZBwg== X-Google-Smtp-Source: AGHT+IFobIXnHuwZ7gLtXd0BFWdrfahlJB49XNeqEtPKjfMjKrp+xxKfVDl60o/t8Wb5NSMNctyvYWSeMpeM6jrEclw= X-Received: by 2002:a17:90a:5c:b0:27c:facc:e3eb with SMTP id 28-20020a17090a005c00b0027cfacce3ebmr20201229pjb.31.1699098085238; Sat, 04 Nov 2023 04:41:25 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?B?7J207IOB7JuQ?= Date: Sat, 4 Nov 2023 20:41:13 +0900 Message-ID: Subject: Connection Timeout Issue due to intermittent non-response of Postgre database To: pgsql-jdbc@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000cf2d1306095219c9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000cf2d1306095219c9 Content-Type: text/plain; charset="UTF-8" Hi. Guru... We are currently applying and testing Postgre Database version 16.0 in the web application. The technology stack of the web application is as follows. - DB OS: Rocky Linux 9.2 - Spring 5.0 Framework (not Spring Boot) - Java: OpenJDK 17 - WAS: Tomcat 9.0 The Postgre database does not respond intermittently, causing a connection timeout in the Spring Framework. There is no regularity in the occurrence of connection timeouts and they do not repeat continuously. Not easy to track. Do you have any experience with cases like this? If you have experience, we need your help to solve the problem. First, I will try to downgrade to version 15.4 to determine whether it is a software problem or a network and server environment. --000000000000cf2d1306095219c9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi. Guru...

We are currently applying a= nd testing Postgre Database version 16.0 in the web application. The techno= logy stack of the web application is as follows.

- DB OS: Rocky Linu= x 9.2
- Spring 5.0 Framework (not Spring Boot)
- Java: OpenJDK 17
= - WAS: Tomcat 9.0

The Postgre database does not respond intermittent= ly, causing a connection timeout in the Spring Framework. There is no regul= arity in the occurrence of connection timeouts and they do not repeat conti= nuously. Not easy to track.

Do you have any experience with cases li= ke this? If you have experience, we need your help to solve the problem.
First, I will try to downgrade to version 15.4 to determine whether it= is a software problem or a network and server environment.
--000000000000cf2d1306095219c9--