From: David Wall <d.wall@computer.org>
To: pgsql-interfaces@postgresql.org
Subject: Re: ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query
Date: Sat, 21 Apr 2001 17:05:55 -0700
Message-ID: <003501c0cac0$00217c60$5a2b7ad8@expertrade.com> (raw)
References: <000e01c0cab8$fec39e40$5a2b7ad8@expertrade.com>
> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: d.wall@computer.org
Subject: Re: ERROR: SET TRANSACTION ISOLATION LEVEL must be called before any query
In-Reply-To: <003501c0cac0$00217c60$5a2b7ad8@expertrade.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox