From: Rachel Greenham <rachel@enlarion.demon.co.uk>
To: pgsql-interfaces@postgresql.org
Subject: JDBC6.5-1.2 other possible problems
Date: Thu, 24 Jun 1999 14:12:58 +0100
Message-ID: <37722EDA.65C55C9D@enlarion.demon.co.uk> (raw)
How/when does the JDBC actually release a postgres connection? I ask
because, when I try running stuff under native threads on Linux, unless
I explicitly close a connection it's left open after the Connection
object itself has gone out of scope - it's visible as a "postgres" task
in the task display, and isn't recovered until the JVM itself has been
killed. Also, it seems that if too many of them occur I get another
major error and the postgres back-end dies.
Platform (sorry, didn't mention in other post):
SuSE Linux 6.0 kernels 2.0.36 and 2.2.9, SMP and not, Blackdown Java
1.2, LiveSoftware's JRunPro servlet engine, Postgres 6.5. This problem
seems to manifest when running under native threads, which is not
*officially* working yet, but seems to.
Is the Postgres JDBC driver thread safe?
--
Rachel
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: rachel@enlarion.demon.co.uk
Subject: Re: JDBC6.5-1.2 other possible problems
In-Reply-To: <37722EDA.65C55C9D@enlarion.demon.co.uk>
* 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