Received: from mail1.expertrade.com (r87-43-dsl.sea.lightrealm.net [216.122.43.87]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3M05t380934 for ; Sat, 21 Apr 2001 20:05:55 -0400 (EDT) (envelope-from d.wall@computer.org) Received: from reggae (reggae.expertrade.com [216.122.43.90]) by mail1.expertrade.com (8.9.3/8.9.3) with SMTP id RAA03343 for ; Sat, 21 Apr 2001 17:05:53 -0700 Message-ID: <003501c0cac0$00217c60$5a2b7ad8@expertrade.com> Reply-To: "David Wall" From: "David Wall" To: References: <000e01c0cab8$fec39e40$5a2b7ad8@expertrade.com> Subject: Re: ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query Date: Sat, 21 Apr 2001 17:05:55 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Archive-Number: 200104/96 X-Sequence-Number: 1480 > Message: ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query Oops. Sorry. It looks like it was a bug in the connection pool class that I've been magically using for a couple of years now. Apparently the usage just never ran into the problem, or there's a difference in the Tomcat servlet engine I'm using that was driving the database. The code was reusing the connection for all pool calls from the same thread, and this somehow created the conflict, probably because of the threadpools used in Tomcat. David