From: | 이상원 <swlee(dot)kioplo(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-jdbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: Connection Timeout Issue due to intermittent non-response of Postgre database |
Date: | 2023-11-06 00:45:00 |
Message-ID: | CALFNBwc86ueiFq528jmeEMNkK0mearWMB3NaaY_5PdYWSxdpmQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Thanks, I'll check it out. then, I will update to all.
2023년 11월 5일 (일) 오전 12:33, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>님이 작성:
> =?UTF-8?B?7J207IOB7JuQ?= <swlee(dot)kioplo(at)gmail(dot)com> 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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2023-11-08 16:50:18 | Re: Connection Timeout Issue due to intermittent non-response of Postgre database |
Previous Message | Tom Lane | 2023-11-04 15:33:06 | Re: Connection Timeout Issue due to intermittent non-response of Postgre database |