Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 65CCE9FB248; Thu, 28 Sep 2006 20:14:01 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 81713-08; Thu, 28 Sep 2006 20:13:57 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from yass.opencloud.co.nz (yass.opencloud.co.nz [131.203.101.226]) by postgresql.org (Postfix) with ESMTP id 5E78D9FA666; Thu, 28 Sep 2006 20:13:54 -0300 (ADT) Received: from 222-153-172-120.jetstream.xtra.co.nz ([222.153.172.120] helo=[10.1.1.3]) by yass.opencloud.co.nz with asmtp (TLS-1.0:DHE_RSA_AES_128_CBC_SHA:16) (Exim 4.34) id 1GT54f-0005an-QC; Fri, 29 Sep 2006 11:13:50 +1200 Message-ID: <451C5725.4070905@opencloud.com> Date: Thu, 28 Sep 2006 23:13:41 +0000 From: Oliver Jowett User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sriram Dandapani CC: pgsql-jdbc@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [JDBC] number of transactions doubling References: <6992E470F12A444BB787B5C937B9D4DF060E5B05@ca-mail1.cis.local> In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF060E5B05@ca-mail1.cis.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/351 X-Sequence-Number: 23265 Sriram Dandapani wrote: > Autocommit is set to off once a connection is obtained from the jboss > pool. It is turned back on when it is closed (so that any idle > transactions are committed). Don't know what to suggest then -- if autocommit is off then the JDBC driver should be sending BEGIN before the first query & COMMIT or ROLLBACK when you explicitly delimit a transaction. There's nothing special about batches. You could set loglevel=2 as a JDBC URL parameter to see exactly what the JDBC driver is sending, perhaps. Or turn on logging on the server side, though I'm not sure at exactly which server version the logging of the extended query protocol became useful. -O