You wouldn't have happened to get any "Broken pipe"
errors like the following, because I am having a
problem with this and cannot figure out what is
causing it?
java.sql.SQLException: IOError while reading from
backend:
java.net.SocketException: Broken pipe
at
postgresql.PG_Stream.ReceiveChar(PG_Stream.java:183)
at
postgresql.Connection.ExecSQL(Connection.java:668)
at
postgresql.Connection.setAutoCommit(Connection.java:377)
--- Holger Klawitter <lists@klawitter.de> wrote:
> Hi Barry,
>
> > Have you tried the latest jdbc build for 7.3 from
> the website? There
> > was a recent bug fix that looks similar to what
> you are reporting here.
>
> I tried the newest version, it also created the same
> problem. But I discovered
> something new:
>
> The "killer" statement had a (char)0 as part of one
> argument. The statement
> seemed to be broken up into two "packets" being sent
> to postgres seperately.
> I am not sure whether the character originated from
> a parameter being sent to
> the webapp or from tomcat dropping one in or even
> jdbc doing so (unlikely).
>
> After the sql exception (unterminated ' constant) I
> got another error only in
> postgres (bad socket command ') which was probably
> from the beginning of the
> "second" packet.
>
> This results in the jdbc driver to be utterly
> confused and closing all
> connection sockets.
>
> Right now I've added an input filter against char
> 0's ...
>
> With kind regards / mit freundlichem Gru�
> Holger Klawitter
> --
> Holger Klawitter
> http://www.klawitter.de
> lists@klawitter.de
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
