| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Idle_session_timeout |
| Date: | 2023-10-04 15:51:19 |
| Message-ID: | 4DA883D1-36E4-455D-9998-50FAA41EA0F0@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On Oct 4, 2023, at 9:38 AM, Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com> wrote:
>
> So, I thought of automating it and set the parameter idle_session_timeout to 5min. But I got a message from application team that they are getting jdbc error continuously and they are saying connection is getting terminated. So I had to turn it off now.
You're not doing anything incorrectly. You just have a mismatch between expectations on the database vs application side.
Either:
the application is allowed to keep connections open permanently, and the database has to be configured to support enough connections
-OR-
the database has a more limited number of connections, and the application manages connecting and disconnecting
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Goran Pulevic | 2023-10-04 16:23:22 | Re: Idle_session_timeout |
| Previous Message | Rajesh Kumar | 2023-10-04 15:38:59 | Idle_session_timeout |