pg.ddx.io pgsql-interfaces@postgresql.org mailing list archivehelp / color / mirror / Atom feed
JDBC6.5-1.2 other possible problems 2+ messages / 2 participants [nested] [flat]
* JDBC6.5-1.2 other possible problems @ 1999-06-24 13:12 Rachel Greenham <rachel@enlarion.demon.co.uk> 0 siblings, 0 replies; 2+ messages in thread From: Rachel Greenham @ 1999-06-24 13:12 UTC (permalink / raw) To: pgsql-interfaces 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
* RE: [INTERFACES] JDBC6.5-1.2 other possible problems @ 1999-06-24 14:38 Peter Mount <petermount@it.maidstone.gov.uk> 0 siblings, 0 replies; 2+ messages in thread From: Peter Mount @ 1999-06-24 14:38 UTC (permalink / raw) To: 'Rachel Greenham' <rachel@enlarion.demon.co.uk>; pgsql-interfaces Currently it's released when the close() method is called. As for thread safe, it is. There's even a thread safety test in the src/jdbc/example directory. Peter -- Peter Mount Enterprise Support Maidstone Borough Council Any views stated are my own, and not those of Maidstone Borough Council. -----Original Message----- From: Rachel Greenham [mailto:rachel@enlarion.demon.co.uk] Sent: Thursday, June 24, 1999 2:13 PM To: pgsql-interfaces@postgreSQL.org Subject: [INTERFACES] JDBC6.5-1.2 other possible problems 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 ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1999-06-24 14:38 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 1999-06-24 13:12 JDBC6.5-1.2 other possible problems Rachel Greenham <rachel@enlarion.demon.co.uk> 1999-06-24 14:38 RE: [INTERFACES] JDBC6.5-1.2 other possible problems Peter Mount <petermount@it.maidstone.gov.uk>
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