Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 619A79FCB9B for ; Fri, 9 Nov 2007 19:03:33 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 82778-04-3 for ; Fri, 9 Nov 2007 19:03:24 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 3C1839F9703 for ; Fri, 9 Nov 2007 19:03:12 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lA9N36nn003994; Fri, 9 Nov 2007 18:03:06 -0500 (EST) To: "Scott Marlowe" cc: "Tena Sakai" , pgsql-admin@postgresql.org Subject: Re: idle in transaction...unexpected EOF on client connection In-reply-to: References: Comments: In-reply-to "Scott Marlowe" message dated "Fri, 09 Nov 2007 16:41:34 -0600" Date: Fri, 09 Nov 2007 18:03:06 -0500 Message-ID: <3993.1194649386@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/86 X-Sequence-Number: 27329 "Scott Marlowe" writes: > Hmmm. Well, when you see an error like unexpected EOF on client > connection then that means that the client "disappeared" without > closing the connection, or the network connection went away. More specifically, the client didn't send the expected "terminate session" message before dropping the network connection. I seem to recall that old versions of the JDBC driver had a bad habit of not sending Terminate --- what JDBC version are you using? regards, tom lane