On 26 November 2015 at 11:35, Fabio Caiut <caiut@hotmail.com> wrote:
Hi,
Vladimir, Thomas ... you're right.
The glassfish guys analyzed dumps and look in the glassfish sources, the problem is there.
They told me pool calls setClientInfo for each query!!
Thank you for your help.
Caiut
> Date: Wed, 25 Nov 2015 19:54:56 +0300 > Subject: Re: [JDBC] How to avoid SET application_name = '' > From: sitnikov.vladimir@gmail.com > To: caiut@hotmail.com > CC: pgsql-jdbc@postgresql.org > > As far as I can tell, there is no option to completely disable "set > application_name" feature via property. > > Is SQL appears when client calls > Connection#setClientInfo("ApplicationName", ...) or > Connection#setClientInfo(Properties). > > It make sense to avoid setting the same application name again and > again for the same connection. > Can you please file an issue at https://github.com/pgjdbc/pgjdbc/issues? > > In the mean time, it would be good if you could capture thread dumps > from the application (e.g. 100 dumps with 10 second intervals under > typical load) and grep setClientInfo. That would point out the line in > code that issues that excessive setClientInfo. > > Vladimir
