Message-ID: <37b909eb3a90ce66315ff88d62f122a47399b720.camel@cybertec.at>
Subject: Re: Idle_session_timeout
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Rajesh Kumar <rajeshkumar.dba09@gmail.com>, Pgsql-admin
	 <pgsql-admin@lists.postgresql.org>
Date: Wed, 04 Oct 2023 22:34:44 +0200
In-Reply-To: 
 <CAJk5AtZ9b11Jbahr8upTgtdq_sNCvqmoQVNH1drPxSKPZsYLWg@mail.gmail.com>
References: 
	<CAJk5AtZ9b11Jbahr8upTgtdq_sNCvqmoQVNH1drPxSKPZsYLWg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/37b909eb3a90ce66315ff88d62f122a47399b720.camel%40cybertec.at>
Precedence: bulk

On Wed, 2023-10-04 at 21:08 +0530, Rajesh Kumar wrote:
> I was facing issue with idle connections not closed.
>=20
> 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 erro=
r
> continuously and they are saying connection is getting terminated.
> So I had to turn it off now.

Yes, if the connection is forcibly closed by the server, the client won't b=
e happy.

If you say "idle connections not closed", that is the fault of the applicat=
ion.
The application has to explicitly close all connections it does not need an=
y more.

Yours,
Laurenz Albe