Re: JDBC causing the connection to close after executing a COPY command - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: JDBC causing the connection to close after executing a COPY command
Date
Msg-id Pine.BSO.4.64.0712131126070.28251@leary.csoft.net
Whole thread Raw
In response to Re: JDBC causing the connection to close after executing a COPY command  (Altaf Malik <mmalik_altaf@yahoo.com>)
Responses Re: JDBC causing the connection to close after executing a COPY command
List pgsql-jdbc

On Thu, 13 Dec 2007, Altaf Malik wrote:

> Also if i enable logging in JDBC, and only execute the COPY statement,
> log shows that FrontEnd sent a Terminate message.
>

What's happening is that after receiving the server's message that it
wants to do a COPY, the driver doesn't understand the protocol and dies
with an "java.io.IOException: Unexpected packet type: " error.  Once this
happens the driver can't do anything but close the connection.  As part of
the connection closing process it issues a Terminate message to the
server, in case it's still listening and the protocol is in a good enough
state that the server might receive it.  The driver is not explicitly
terminating the connection upon receiving a copy request, that's just what
happens when it gets confused.

Kris Jurka

pgsql-jdbc by date:

Previous
From: Kris Jurka
Date:
Subject: Re: JDBC causing the connection to close after executing a COPY command
Next
From: Kris Jurka
Date:
Subject: Re: Synthesize support for Statement.getGeneratedKeys()?