Hi-
I'm pretty sure that the connection problems are the source of the large
object descriptor error, not the other way around.
Essentially, these messages tell you that the backend lost communication
with the client unexpectedly. (I'm assuming JDBC client.) One of the common
sources of this problem that other folks have encountered is the presence of
firewall or other network security software that allows the initial
connection to be negotiated and then stops subsequent packets.
-Nick
--------------------------------------------------------------------------
Nick Fankhauser nickf@ontko.com Phone 1.765.935.4283 Fax 1.765.962.9788
Ray Ontko & Co. Software Consulting Services http://www.ontko.com/
-----Original Message-----
From: pgsql-jdbc-owner@postgresql.org
[mailto:pgsql-jdbc-owner@postgresql.org]On Behalf Of covadonga rodriguez
Sent: Thursday, May 16, 2002 4:38 AM
To: pgsql-jdbc@postgresql.org
Subject: [JDBC] lo_close: invalid large obj descriptor (0)
we have the following error:
"pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: recv() failed: Connection reset by peer
pq_recvbuf: recv() failed: Connection reset by peer
pq_recvbuf: recv() failed: Connection reset by peer
ERROR: lo_close: invalid large obj descriptor (0)
NOTICE: current transaction is aborted, queries ignored until end of
transaction block"
and autoCommit is always set to 'false' in our system, we don't know what to
do? please, help!
Do You Yahoo!?
Yahoo! Messenger!
Comunicación instantánea gratis con tu gente.
