From: | Bosco Rama <postgres(at)boscorama(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: unexpected close |
Date: | 2013-11-11 17:25:05 |
Message-ID: | 528112F1.70005@boscorama.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 11/09/13 01:57, John R Pierce wrote:
> but it looks like the app was packaged with a rather old JDBC,
> postgresql-8.3-604.jdbc3.jar
> our java apps do only the most basic sql APIs, all data is numbers and
> varchar, this jdbc worked fine with older versions.
>
> is this a error likely because of this old JDBC with the newer 9.2 server?
Just a random observation (and probably wrong for this, but ...) we
used to see these sorts of errors within ecpg and/or libpq when a
connection got used by multiple threads simultaneously. But, IIRC, PG
jdbc connections are thread-safe. Unless they weren't in the '8.3' era.
(Relatively new to PG's jdbc so take with appropriately sized grain of
salt :-p ).
Bosco.
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Eriksson | 2013-11-18 14:57:21 | preparedStatement, Batch, DEFAULT, getGeneratedKeys() |
Previous Message | Dave Cramer | 2013-11-11 11:30:05 | Re: unexpected close |