| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Altaf Malik <mmalik_altaf(at)yahoo(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC causing the connection to close after executing a COPY command |
| Date: | 2007-12-13 16:36:18 |
| Message-ID: | Pine.BSO.4.64.0712131126070.28251@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kris Jurka | 2007-12-13 16:49:18 | Re: Synthesize support for Statement.getGeneratedKeys()? |
| Previous Message | Kris Jurka | 2007-12-13 16:26:03 | Re: JDBC causing the connection to close after executing a COPY command |