Re: invalid message format and I/O error while comunicating with backend - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: invalid message format and I/O error while comunicating with backend
Date
Msg-id Pine.BSO.4.64.0804141130030.5378@leary.csoft.net
Whole thread Raw
In response to Re: invalid message format and I/O error while comunicating with backend  (Sergi Vera <svera@emovilia.com>)
List pgsql-jdbc

On Mon, 14 Apr 2008, Sergi Vera wrote:

> ERROR:  message format invalid
> FATAL:  message type of frontend 0 is not valid
>
> Besides this <unnamed> that appears on the sentences not much more info
> is shown on the logs.
> Sometimes the number associated whith the fronted changes Sometimes it's
> 0 sometimes it's 255..
>

This makes it look like the JDBC driver is doing something wrong when
calculating a message length or message content for the frontend/backend
protocol.  If you've got a self-contained test case we could take a
look at that.  If not can you try adding loglevel=2 to your JDBC URL to
get debugging information from the driver?  Also capturing the network
traffic with tcpdump would be interesting.

Kris Jurka

pgsql-jdbc by date:

Previous
From: Stanislav Mironov
Date:
Subject: Re: Two BLOBs (OID) in table?
Next
From: Kris Jurka
Date:
Subject: Re: Two BLOBs (OID) in table?