From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | zxcv(at)infoweb(dot)cz |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: SocketException: Connection reset |
Date: | 2009-02-20 00:42:53 |
Message-ID: | 499DFC8D.5060307@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
zxcv(at)infoweb(dot)cz wrote:
> \"jdbc:postgresql://localhost:5432/my\", propsDB);
> attempt number 69
> Exception in thread \"main\"
> org.postgresql.util.PSQLException: The connection
> attempt failed.
> Caused by: java.net.SocketException: Connection
> reset
> at
> java.net.SocketInputStream.read(SocketInputStream.java:168)
> org.postgresql.core.PGStream.ReceiveChar(PGStream.java:259)
> at
> org.postgresql.core.v2.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:207)
Does anything appear in the PostgreSQL server logs? Try turning up
logging verbosity and see if you get anything informative when logging
is set to debug level.
Do you have a virus scanner or firewall product installed on the
machine? If so, does the problem go away if you UNINSTALL (not merely
disable) the product then run "netsh interface ip reset c:\resetlog.txt"
in cmd.exe ? I repeat, in many cases disabling firewall/AV products is
NOT sufficient, they must often be UNINSTALLED to get rid of the filter
drivers that cause problems.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Vlad Arkhipov | 2009-02-20 02:30:53 | Feature Request: some of non JDBC types should implement Comparable |
Previous Message | zxcv | 2009-02-19 16:46:06 | SocketException: Connection reset |