Skip site navigation (1) Skip section navigation (2)

Socket read fails

From: Colin Taylor <colin(dot)taylor(at)gmail(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Socket read fails
Date: 2006-01-16 03:35:29
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
Hi there, wondering if anyone could shed some light on selects
intermittently not returning any data on our production server.

Symptoms are:

- occurs in several different parts of our codebase but apparently its the
same jdbc codepath [below]
- these codepaths execute fine the vast majority of the time
- thread blocks on read forever
- database doesnt show any query running.
- system has a couple of high load processes that run every day and we only
see the errors there, though the majority of the systems' queries are done

Any suggestions for what I could do to fix or help diagnose the problem
greatly appreciated. We saw these problems with v7, v8 and now seeming more
frequently (ie every few days) with 8.1 jdbc and 8.1 server.

We run ES Linux 3.


"Thread-571" prio=1 tid=0x085745b0 nid=0x124e runnable [759fe000..759ff87c]
        at Method)
        - locked <0x847ac890> (a
        at org.postgresql.core.PGStream.Receive(
        at org.postgresql.core.PGStream.Receive(
        at org.postgresql.core.PGStream.ReceiveTupleV3(
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(
        at org.postgresql.core.v3.QueryExecutorImpl.fetch(
        - locked <0x847aa0b0> (a org.postgresql.core.v3.QueryExecutorImpl)


pgsql-jdbc by date

Next:From: Minal A. AryamaneDate: 2006-01-16 08:33:48
Subject: Stored Procedures
Previous:From: Joeseph BlowsephDate: 2006-01-14 22:05:26
Subject: Re: 'FATAL: database "null" does not exist ' when accessing through a

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group