Re: BUG #15957: Connection event listener not called during close()

From: Dave Cramer <davecramer(at)gmail(dot)com>
To: prakashprabhu87(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15957: Connection event listener not called during close()
Date: 2019-08-20 12:59:43
Message-ID: CADK3HHJb8LOO_u8TvzdKa6P9f9hhqoO5XGMbRfEUiBZSGN4k7A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 13 Aug 2019 at 18:37, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 15957
> Logged by: Prakash Prabhu Bantwal
> Email address: prakashprabhu87(at)gmail(dot)com
> PostgreSQL version: Unsupported/Unknown
> Operating system: linux
> Description:
>
> Hi,
>
> Testing with version
>
> <dependency>
> <groupId>org.postgresql</groupId>
> <artifactId>postgresql</artifactId>
> <version>42.2.5</version>
> </dependency>
>
>
> I am using postgres with hibernate and during the close() call from the
> Jdbc
> template is called, the connectionClosed() from the event listner is not
> being called. i see the listener is being invoked from
> fireConnectionClosed() but this should also be invoked from close() method.
>

Pretty sure this is a hibernate thing. The JDBC API does not have an event
listener interface that fires on connectionClosed.

Dave

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Janes 2019-08-20 13:44:55 Re: BUG #15967: Sequence generation using NEXTVAL() fails on 64bit systems
Previous Message Dave Cramer 2019-08-20 12:57:18 Re: BUG #15939: Postgres database size is growing due to oraphan objects