Great point. I even found some ID 4226 from around that time a few days ago. However, I cleared my event log, repeated
thetest and the issue, and no entries appeared in the event log. So although this sounds promising, it doesn't appear
tobe the case.
----- Original Message ----
From: Donald Fraser <postgres@kiwi-fraser.net>
To: [JDBC] <pgsql-jdbc@postgresql.org>
Sent: Thursday, August 20, 2009 7:22:38 AM
Subject: Re: [JDBC] JDBC broken connection against Postgres 8.4
I note from your original email that your test platform is Windows XP.
Please check the system event logs for ID 4226.
If you see this message then you have a TCP connection limit issue causing problems.
----- Original Message ----- From: ??????? ????????
To: Michael Bell
Cc: pgsql-jdbc@postgresql.org
Sent: Thursday, August 20, 2009 1:09 PM
Subject: Re: [JDBC] JDBC broken connection against Postgres 8.4
May be, you have a firewall software that is working and can't keep up with all this connections opened over loopback?
2009/8/17 Michael Bell <mikebell90@yahoo.com>
As you see below, something seems....whacked. A simple loop with an unpooled connection (code provided below) often
givesan exception when connecting. The Thread.sleep statement has been made as high as 5000 ms, and exceptions still
sporadicallyoccur.
I don't know if this is a JDBC driver issue or core server issue. Or something here. But the code is so simple....
-- Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
