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

From Sergi Vera
Subject Re: invalid message format and I/O error while comunicating with backend
Date
Msg-id 48031029.2090409@emovilia.com
Whole thread Raw
In response to Re: invalid message format and I/O error while comunicating with backend  (Sergi Vera <svera@emovilia.com>)
Responses Re: invalid message format and I/O error while comunicating with backend  (Kris Jurka <books@ejurka.com>)
List pgsql-jdbc
Adding more logs doesn't give any more clue:<br /> (...)<br /><br /> LOG:  sentencia: EXECUTE <unnamed> 
[PREPARE: COMMIT]<br /> LOG:  sentencia: <BIND> <br /> LOG:  sentencia: EXECUTE <unnamed>  [PREPARE: 
BEGIN]<br/> LOG:  sentencia: <BIND> <br /> LOG:  sentencia: EXECUTE <unnamed>  [PREPARE:  SELECT * FROM
loctest.posicion,loctest.datosensor WHERE id_activo = $1 AND posicion.idposicion = datosensor.idposicion AND idsensor =
2ORDER BY time DESC LIMIT 1]<br /> LOG:  sentencia: <BIND> <br /> LOG:  sentencia: EXECUTE <unnamed> 
[PREPARE: SELECT * FROM loctest.posicion, loctest.datosensor WHERE id_activo = $1 AND posicion.idposicion =
datosensor.idposicionAND idsensor = 2 ORDER BY time DESC LIMIT 1]<br /> LOG:  sentencia: <BIND> <br /> LOG: 
sentencia:EXECUTE <unnamed>  [PREPARE:  SELECT * FROM loctest.pois]<br /> LOG:  sentencia: <BIND> <br />
LOG: sentencia: EXECUTE <unnamed>  [PREPARE:  SELECT * FROM loctest.pois]<br /> LOG:  sentencia: <BIND> <br
/>LOG:  sentencia: EXECUTE <unnamed>  [PREPARE:  SELECT current FROM loctest.id_pos_seq_view]<br /> LOG: 
sentencia:<BIND> <br /> LOG:  sentencia: EXECUTE <unnamed>  [PREPARE:  SELECT current FROM
loctest.id_pos_seq_view]<br/> LOG:  sentencia: <BIND> <br /> ERROR:  message format invalid<br /> FATAL:  message
typeof frontend 0 is not valid<br /><br /><br /> Besides this <unnamed> that appears on the sentences not much
moreinfo is shown on the logs.<br /> Sometimes the number associated whith the fronted changes Sometimes it's 0
sometimesit's 255..<br /><br /> Regards<br /><br /> Sergi Vera escribió: <blockquote
cite="mid:48030B0A.1070404@emovilia.com"type="cite"><br /> Thanks Craig, <br /><br /> Browsing the pgsql logs I've
foundthe following error messages (roughly translated to english): <br /><br /> (autovacuums) <br /> ... <br />
(autovacuums)<br /> ERROR: remaining data on the message is not sufficient <br /> FATAL: message type from the frontend
0is not valid <br /><br /> I just don't understand why sometimes it fails and sometimes not. <br /><br /> I will try
theother suggestion you made as soon as possible <br /><br /> Craig Ringer escribió: <br /><blockquote
type="cite">SergiVera wrote: <br /><br />   <blockquote type="cite">Everything is working ok and fast, but at some
moment(sometimes sooner, <br /> sometimes later) the server starts to fail with the following messages <br /><br />
org.postgresql.util.PSQLException:invalid message format (for the first <br /> failure) <br />
org.postgresql.util.PSQLException:A I/O error has happened while <br /> sending to backend (at every following jdbc
call)<br />     </blockquote><br /> I suggest having a look in the server logs to see if there is any error <br />
beingreported by the backend. <br /><br /> You might also find it helpful to enable log_statement and <br />
log_connectionin postgresql.conf while you're trying to track the issue <br /> down. Your logs might get quite big if
yourload is high, though. <br /><br /> -- <br /> Craig Ringer <br /><br />   </blockquote><br /><br /></blockquote><br
/><br/><div class="moz-signature">-- <br /></div><a href="http://www.emovilia.com/"> <img border="0"
src="cid:part1.00080804.01070300@emovilia.com"/></a><p style="margin-bottom: 0cm;">Sergio Vera<br /> Rosellón, 34, 5
Planta<br/> 08029 Barcelona<br /> tel. 902101870<br /><a class="moz-txt-link-abbreviated"
href="http://www.emovilia.com">www.emovilia.com</a><br/><br /><p lang="ca-ES" style="margin-bottom: 0cm;"><font
face="Consolas,monospace" size="2" style="font-size: 10pt;">IMPRIME ESTE EMAIL Y SUS ARCHIVOS SI REALMENTE LOS
NECESITAS.<br/> GRACIAS POR RESPETAR EL MEDIO AMBIENTE.</font><p lang="ca-ES" style="margin-bottom: 0cm;"><font
face="Consolas,monospace"><font size="2" style="font-size: 10pt;">NOTA: La información contenida en este email, y sus
documentosadjuntos, es confidencial y para uso exclusivo de la persona o personas a las que va dirigido. No está
permitidoel acceso a este mensaje a otra persona distinta a los indicados. Si no es uno de los destinatarios o ha
recibidoeste mensaje por error, cualquier duplicación, reproducción, distribución, así como cualquier uso de la
informacióncontenida o cualquiera otra acción tomada en relación con el mismo, está prohibida y puede ser
ilegal.</font></font><plang="ca-ES" style="margin-bottom: 0cm;"><p lang="ca-ES" style="margin-bottom: 0cm;"><p
lang="ca-ES"style="margin-bottom: 0cm;"><font face="Consolas, monospace"><font size="2" style="font-size:
10pt;">ADVICE:The information in this email as in the attachments is confidential and private for exclusive use of the
targetuser group. Access to this message is disallowed to any other than the addressee. If you are not the addressee or
youhave been included by mistake, any duplication, reproduction, distribution as any other action relative to this
emailis strictly forbidden and might be illegal.</font></font> 

pgsql-jdbc by date:

Previous
From: Sergi Vera
Date:
Subject: Re: invalid message format and I/O error while comunicating with backend
Next
From: Stanislav Mironov
Date:
Subject: Re: Two BLOBs (OID) in table?