Re: Question about JDBC?

Nick,

Just to clarify, it's not suspicous traffic. What actually happens is
that the connection is masqueraded, and masq'd connections have timeouts
on them, so if there is no activity for a certain amount of time they
get closed.

Dave
On Thu, 2002-08-22 at 08:07, Nick Fankhauser wrote:
> Alex-
>
> Other developers have gotten this message when Firewall or other security
> software breaks a connection that has already been established. Apparently
> some security software thinks that activity on port 5432 is suspicious.
> Regardless of what is causing it, the important piece of information is
> "java.net.SocketException: Broken pipe", which is telling you that either
> the back end disapppeared unexpectedly, or the network connection was
> broken.
>
> Regards,
>
> -Nick
>
> > -----Original Message-----
> > From: pgsql-jdbc-owner(at)postgresql(dot)org
> > [mailto:pgsql-jdbc-owner(at)postgresql(dot)org]On Behalf Of Alejandro Vergara
> > Sent: Wednesday, August 14, 2002 2:11 PM
> > To: pgsql-jdbc(at)postgresql(dot)org; alexvt(at)ife(dot)org(dot)mx
> > Subject: [JDBC] Question about JDBC?
> >
> >
> > Hi sometimes I catch this exceptions in my aplications:
> > *************************************************
> > 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)
> > at actas2003.partidos.Partidos.doGet(PartidosPoliticos.java:45)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:499)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
> > at
> > org.apache.jserv.JServConnection.processRequest(JServConnection.java:335)
> >
> > at
> > org.apache.jserv.JServConnection.run(JServConnection.java:197)
> > at java.lang.Thread.run(Thread.java)
> > java.sql.SQLException: Error flushing output: java.io.IOException:
> > Broken pipe
> > at postgresql.PG_Stream.flush(PG_Stream.java:370)
> > at postgresql.Connection.ExecSQL(Connection.java:659)
> > at postgresql.Connection.setAutoCommit(Connection.java:377)
> > at
> > actas2003.funcionarios.catalogo.BuscaFun.doGet(BuscaFun.java:67)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:499)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
> > at
> > org.apache.jserv.JServConnection.processRequest(JServConnection.java:335)
> >
> > at
> > org.apache.jserv.JServConnection.run(JServConnection.java:197)
> > at java.lang.Thread.run(Thread.java)
> > java.sql.SQLException: Error flushing output: java.io.IOException:
> > Broken pipe
> > at postgresql.PG_Stream.flush(PG_Stream.java:370)
> > at postgresql.Connection.ExecSQL(Connection.java:659)
> > at postgresql.Connection.setAutoCommit(Connection.java:377)
> > at
> > actas2003.funcionarios.catalogo.DatosFun.doGet(DatosFun.java:68)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:499)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
> > at
> > org.apache.jserv.JServConnection.processRequest(JServConnection.java:335)
> >
> > at
> > org.apache.jserv.JServConnection.run(JServConnection.java:197)
> > at java.lang.Thread.run(Thread.java)
> > **********************************************************
> > We don't know if the error is in the driver or is our aplications, the
> > extrange is that is not common error, and when ocurred is solved by
> > restarting postgres...
> >
> > The thing that we want to know is if someone can help us to found the
> > reason to this error to take actions about it.
> >
> > Thanks for all.
> >
> > Alex...
> >
> >
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 6: Have you searched our list archives?
> >
> > http://archives.postgresql.org
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>