public inbox for [email protected]help / color / mirror / Atom feed
Connection Timeout Issue due to intermittent non-response of Postgre database 4+ messages / 3 participants [nested] [flat]
* Connection Timeout Issue due to intermittent non-response of Postgre database @ 2023-11-04 11:41 이상원 <[email protected]> 2023-11-04 15:33 ` Re: Connection Timeout Issue due to intermittent non-response of Postgre database Tom Lane <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: 이상원 @ 2023-11-04 11:41 UTC (permalink / raw) To: [email protected] 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. ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Connection Timeout Issue due to intermittent non-response of Postgre database 2023-11-04 11:41 Connection Timeout Issue due to intermittent non-response of Postgre database 이상원 <[email protected]> @ 2023-11-04 15:33 ` Tom Lane <[email protected]> 2023-11-06 00:45 ` Re: Connection Timeout Issue due to intermittent non-response of Postgre database 이상원 <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: Tom Lane @ 2023-11-04 15:33 UTC (permalink / raw) To: 이상원 <[email protected]>; +Cc: [email protected] =?UTF-8?B?7J207IOB7JuQ?= <[email protected]> writes: > 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. I'd try turning on statement logging, and maybe also statement duration logging, and then matching up the times of observed client-side outages with what's happening according to the postmaster log. Connection and disconnection logging might be useful too. A likely bet about the root cause is an unreasonably short connection timeout in some network infrastructure between your client and the database server. That would manifest as both sides reporting that the other side disconnected (not necessarily at the same time, but for the same connection). If so, it could likely be cured by adjusting the database's TCP keepalive settings. But you ought to gather data first. regards, tom lane ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Connection Timeout Issue due to intermittent non-response of Postgre database 2023-11-04 11:41 Connection Timeout Issue due to intermittent non-response of Postgre database 이상원 <[email protected]> 2023-11-04 15:33 ` Re: Connection Timeout Issue due to intermittent non-response of Postgre database Tom Lane <[email protected]> @ 2023-11-06 00:45 ` 이상원 <[email protected]> 2023-11-08 16:50 ` Re: Connection Timeout Issue due to intermittent non-response of Postgre database Dave Cramer <[email protected]> 0 siblings, 1 reply; 4+ messages in thread From: 이상원 @ 2023-11-06 00:45 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: [email protected] Thanks, I'll check it out. then, I will update to all. 2023년 11월 5일 (일) 오전 12:33, Tom Lane <[email protected]>님이 작성: > =?UTF-8?B?7J207IOB7JuQ?= <[email protected]> writes: > > 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. > > I'd try turning on statement logging, and maybe also statement duration > logging, and then matching up the times of observed client-side outages > with what's happening according to the postmaster log. Connection > and disconnection logging might be useful too. > > A likely bet about the root cause is an unreasonably short connection > timeout in some network infrastructure between your client and the > database server. That would manifest as both sides reporting that the > other side disconnected (not necessarily at the same time, but for the > same connection). If so, it could likely be cured by adjusting the > database's TCP keepalive settings. But you ought to gather data > first. > > regards, tom lane > ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Connection Timeout Issue due to intermittent non-response of Postgre database 2023-11-04 11:41 Connection Timeout Issue due to intermittent non-response of Postgre database 이상원 <[email protected]> 2023-11-04 15:33 ` Re: Connection Timeout Issue due to intermittent non-response of Postgre database Tom Lane <[email protected]> 2023-11-06 00:45 ` Re: Connection Timeout Issue due to intermittent non-response of Postgre database 이상원 <[email protected]> @ 2023-11-08 16:50 ` Dave Cramer <[email protected]> 0 siblings, 0 replies; 4+ messages in thread From: Dave Cramer @ 2023-11-08 16:50 UTC (permalink / raw) To: 이상원 <[email protected]>; +Cc: Tom Lane <[email protected]>; [email protected] On Sun, 5 Nov 2023 at 19:45, 이상원 <[email protected]> wrote: > Thanks, I'll check it out. then, I will update to all. > > 2023년 11월 5일 (일) 오전 12:33, Tom Lane <[email protected]>님이 작성: > >> =?UTF-8?B?7J207IOB7JuQ?= <[email protected]> writes: >> > 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. >> >> I'd try turning on statement logging, and maybe also statement duration >> logging, and then matching up the times of observed client-side outages >> with what's happening according to the postmaster log. Connection >> and disconnection logging might be useful too. >> >> A likely bet about the root cause is an unreasonably short connection >> timeout in some network infrastructure between your client and the >> database server. That would manifest as both sides reporting that the >> other side disconnected (not necessarily at the same time, but for the >> same connection). If so, it could likely be cured by adjusting the >> database's TCP keepalive settings. But you ought to gather data >> first. >> > I would have to agree that it is very likely a network issue. Dave ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2023-11-08 16:50 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2023-11-04 11:41 Connection Timeout Issue due to intermittent non-response of Postgre database 이상원 <[email protected]> 2023-11-04 15:33 ` Tom Lane <[email protected]> 2023-11-06 00:45 ` 이상원 <[email protected]> 2023-11-08 16:50 ` Dave Cramer <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox