From: | Michael Bell <mikebell90(at)yahoo(dot)com> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: JDBC Connection broken (followup) |
Date: | 2009-08-17 16:00:42 |
Message-ID: | 417177.39237.qm@web43135.mail.sp1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Thanks for replying. I changed the pg_hba.conf to trust (I don't care about the password, this is just a test system, installed from scratch). However, unfortunately WinPCap cannot capture loopback traffic, so that doesn't help us much :)
Other side notes: tried LSPFix - it found no problems. And I use this box to test MS SQL, MySQL regularly with no issues.
----- Original Message ----
From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: pgsql-jdbc(at)postgresql(dot)org
Sent: Monday, August 17, 2009 3:17:52 AM
Subject: Re: [JDBC] JDBC Connection broken (followup)
On 17/08/2009 4:00 PM, Michael Bell wrote:
> Oh, tried this with Windows firewall off, and AV off too. Here's the logging of the last few successful, and then the unsuccessful....
It might be useful if you could:
- in pg_hba.conf, set 127.0.0.1 to "trust" or change the password
of the user you'll be testing with to something generic; then
- use Wireshark (http://wireshark.org/) to capture traffic on the
loopback interface during a failed login attempt that results in
the "incomplete startup packet" error.
- Change pg_hba.conf back / reset the password you changed
- Post the packet trace (libpcap format) or, if it's too big, put
it up somewhere people can download it and post a link to it.
Doing so may or may not help - but if the results look normal you at least know the client is sending the right startup packet and it's a server side problem.
"An operation was attempted on something that is not a socket" makes you wonder if the socket was closed, the backend is getting FDs (handles) mixed up, or something. I was about to suggest trying to get a log with Process Monitor (from Sysinternals) but it doesn't look like Process Monitor records TCP/IP socket activity, so it won't be much use. Sigh.
Maybe the wireshark trace will be informative...
--
Craig Ringer
> 2009-08-17 00:56:58 PDTLOCATION: BackendInitialize, .\src\backend\postmaster\postmaster.c:3205
> 2009-08-17 00:56:58 PDTLOG: XX000: could not receive data from client: An operation was attempted on something that is not a socket.
> 2009-08-17 00:56:58 PDTLOCATION: pq_recvbuf, .\src\backend\libpq\pqcomm.c:769
> 2009-08-17 00:56:59 PDTLOG: 08P01: incomplete startup packet
> 2009-08-17 00:56:59 PDTLOCATION: ProcessStartupPacket, .\src\backend\postmaster\postmaster.c:1469
>
>
>
>
>
-- Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
From | Date | Subject | |
---|---|---|---|
Next Message | dmp | 2009-08-17 16:31:51 | Re: JDBC connection query.. |
Previous Message | dmp | 2009-08-17 15:48:41 | Re: JDBC broken connection against Postgres 8.4 |