AW: postgres, idle in transaction

From: Oilid Adsi (Oilid.Ads..reenet-ag.de)
Date: Wed Apr 25 2007 - 03:45:23 EDT

  • Next message: Tore Halset: "Re: AW: postgres, idle in transaction"

    Hi Andrus,

    Thanks for the patch!

    I have deployed the patch yesterday and switched to cayenne data source.

    But unfortunately there is no improvement as you supposed before.

    Is there no way to force this "stupid" COMMIT in a transaction?
    Do you have another idea?

    Kind regards
    Oilid

    > -----Ursprüngliche Nachricht-----
    > Von: Andrus Adamchik [mailto:andru..bjectstyle.org]
    > Gesendet: Dienstag, 24. April 2007 17:20
    > An: use..ayenne.apache.org
    > Betreff: Re: postgres, idle in transaction
    >
    > I just uploaded a patched 1.2 build with Cayenne connection pool
    > rolling back transactions before returning them to the pool. Can you
    > try it out (of course resetting DBCP data source back to Cayenne):
    >
    > http://people.apache.org/~aadamchik/patched/cayenne-nodeps-1.2.3-dev.jar
    >
    > I don't have too much hope this will fix it... but still worth a try.
    >
    > Andrus
    >
    >
    > On Apr 24, 2007, at 5:28 PM, Oilid Adsi wrote:
    >
    > >> -----Ursprüngliche Nachricht-----
    > >> Von: Andrus Adamchik [mailto:andru..bjectstyle.org]
    > >> Gesendet: Dienstag, 24. April 2007 16:21
    > >> An: use..ayenne.apache.org
    > >> Betreff: Re: AW: postgres, idle in transaction
    > >>
    > >>
    > >> On Apr 24, 2007, at 5:17 PM, Andrus Adamchik wrote:
    > >>
    > >>> Interesting... Looking at your log I see this:
    > >>>
    > >>> 15:33:08.267 (2) FE=> Parse(stmt=S_1,query="BEGIN",oids={})
    > >>> .....
    > >>> 15:33:08.268 (2) FE=> Parse(stmt=null,query="SELECT ....
    > >>> ....
    > >>> 15:33:28.461 (2) FE=> Parse(stmt=S_2,query="COMMIT",oids={})
    > >>>
    > >>>
    > >>> So transaction is clearly committed. But of course connection is
    > >>> not closed. It is returned to the pool instead. Still looks like a
    > >>> driver bug to me.
    > >>>
    > >>> Andrus
    > >>
    > >> Sorry, you said "sometimes". Just noticed that the first case indeed
    > >> doesn't commit. Just thought of another potential source of leaks -
    > >> Cayenne iterated queries. Are you using any of those?
    > >
    > > No, we are not using performIteratedQuery() with postgres.
    > >
    > > Is there another possibility to debug this problem or verify if
    > > this is maybe a cayenne or jdbc-postgres bug?
    > >
    > > Oilid
    > >

    This archive was generated by hypermail 2.0.0 : Wed Apr 25 2007 - 03:46:18 EDT