From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
---|---|
To: | Howard Cole <howardnews(at)selestial(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Unexpected EOF on client connection |
Date: | 2009-12-01 16:23:00 |
Message-ID: | 396486430912010823q485f3b8fu2159042e77b4d22e@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Dec 1, 2009 at 7:52 AM, Howard Cole <howardnews(at)selestial(dot)com> wrote:
> I am getting many entries in my log of this type:
>
> 2009-12-01 00:13:19 GMTLOG: unexpected EOF on client connection
> 2009-12-01 00:13:19 GMTLOG could not receive data from client: No connection
> could be made because the target machine actively refused it.
>
> I tend to get these message in batches of 2 to 8 - checking the number of
> connections at the time, they do not appear to be overloaded.
>
> I am running 8.4.1 on Windows 2K3 with a C# application using Npgsql. All
> connections are to the localhost and there is no firewall.
I'm going to make a guess that your client application is not
explicitly closing the C# connection objects before the objects go out
of scope. Once the object become eligible for the garbage collector,
its destroyed and then Postgres notices that it can talk to the client
anymore. Hence you get the above mentioned error.
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Figueiredo Jr. | 2009-12-01 16:26:26 | Re: Unexpected EOF on client connection |
Previous Message | Adrian Klaver | 2009-12-01 16:04:15 | Re: import data from openoffice Calc |