pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Koen Martens <pgsql@metro.cx>
To: Doug Lochart <dlochart@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Socket Timeouts and fatal errors (please help)
Date: Mon, 01 May 2006 14:50:54 +0200
Message-ID: <4456042E.3050801@metro.cx> (raw)
In-Reply-To: <1e71f8880604260844l8a6949ana25cf35c3f4a5c6e@mail.gmail.com>
References: <1e71f8880604260844l8a6949ana25cf35c3f4a5c6e@mail.gmail.com>

Doug Lochart wrote:
> Our production server is not used heavily at the moment.  What we are
> experiencing is the following:
> 
> (java side)
> Sporadic (once or twice a month) Socket timeout exceptions like this: 
> The call in question is simply doing some data cleanup when a user
> session expires.  Don't the the word 'Lock' worry you ... its all
> data.  This call failed on a query.
> 
> org.postgresql.util.PSQLException: An I/O error occured while sending
> to the backend.
>         at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:214)
>         at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:430)
>         at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:332)
>         at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:324)
>         at com.capecomputing.mensana.dataaccess.MensanaConnection.getConnection(MensanaConnection.java:116)
>         at com.capecomputing.mensana.dataaccess.MensanaConnection.<init>(MensanaConnection.java:83)
>         at com.capecomputing.mensana.dataaccess.DatabaseUpdateAction.getEncryptedParameters(DatabaseUpdateAction.java:65)
>         at com.capecomputing.mensana.dataaccess.DatabaseUpdateAction.createEncryptedParamterList(DatabaseUpdateAction.java:39)
>         at com.capecomputing.mensana.dataaccess.CleanupLockedPrepaidClientInvoicesAction.<init>(CleanupLockedPrepaidClientInvoicesAction.java:33)
>         at com.capecomputing.mensana.dataaccess.MensanaDataAccess.cleanupLockedPrepaidInvoices(MensanaDataAccess.java:1685)
>         at com.capecomputing.mensana.webportal.application.SessionEventListener.cleanupLockedPrepaidInvoices(SessionEventListener.java:62)
>         ...
> Caused by: java.net.SocketException: Connection timed out
>         at java.net.SocketInputStream.socketRead0(Native Method)
>         at java.net.SocketInputStream.read(SocketInputStream.java:129)
>         at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
>         at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
>         at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:254)
>         at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1163)
>         at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188)
>         ... 49 more

Don't know if it helps, but i had similar problems a while back.
Turned out it was caused by a misconfigured firewall reload
(flushing all the firewall rules followed by re-inserting them)
which caused outstanding network connections to be interrupted.
Doing firewall reload the proper way (load new rules in inactive
table, swap active & inactive) fixed it for me.

> An unexpected exception has been detected in native code outside the VM.
> Unexpected Signal : 11 occurred at PC=0x400EA4D3
> Function=strlen+0x33
> Library=/lib/libc.so.6
> ...

And this I have seen on occasions where the compiled libc was out of
sync with the kernel version used, but might be anything..

Best,

Koen

-- 
K.F.J. Martens, Sonologic, http://www.sonologic.nl/
Networking, hosting, embedded systems, unix, artificial intelligence.
Public PGP key: http://www.metro.cx/pubkey-gmc.asc
Wondering about the funny attachment your mail program
can't read? Visit http://www.openpgp.org/



view thread (2+ messages)

Message-ID: <4456042E.3050801@metro.cx>
Permalink:  ../4456042E.3050801@metro.cx/
Also on:    postgresql.org/message-id/4456042E.3050801@metro.cx

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: pgsql@metro.cx, dlochart@gmail.com
  Subject: Re: Socket Timeouts and fatal errors (please help)
  In-Reply-To: <4456042E.3050801@metro.cx>
  References: <1e71f8880604260844l8a6949ana25cf35c3f4a5c6e@mail.gmail.com> <4456042E.3050801@metro.cx>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox