Re: Unexpected EOF on client connection

Richard Broersma wrote:
> 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.
>
>
I am quite thorough and keep database access restricted to a single
class with strict exception handling to catch errors. And force the
connection to close / force disposal everywhere. But I shall certainly
be checking my code - thanks for the tip.

Interesting what Francis says about the pool connections being closed
before disposal. Presumably I should never get this error if I use Npgsql?