X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id EE4C59FAD5A for ; Mon, 1 May 2006 10:13:00 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 88168-06 for ; Mon, 1 May 2006 10:12:46 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 328B49F9DCD for ; Mon, 1 May 2006 10:12:46 -0300 (ADT) Received: from mx1.sonologic.nl (mx1.sonologic.nl [82.94.245.21]) by svr4.postgresql.org (Postfix) with ESMTP id 5E2FB5B82A9 for ; Mon, 1 May 2006 12:50:48 +0000 (GMT) Received: from [192.168.0.254] (gongmaster.xs4all.nl [213.84.33.240]) (authenticated bits=0) by mx1.sonologic.nl (8.13.6/8.13.6) with ESMTP id k41CodJB046444; Mon, 1 May 2006 12:50:43 GMT Message-ID: <4456042E.3050801@metro.cx> Date: Mon, 01 May 2006 14:50:54 +0200 From: Koen Martens Organization: Sonologic User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050317 Thunderbird/1.0.2 Mnenhy/0.7.2.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Lochart Cc: pgsql-admin@postgresql.org Subject: Re: Socket Timeouts and fatal errors (please help) References: <1e71f8880604260844l8a6949ana25cf35c3f4a5c6e@mail.gmail.com> In-Reply-To: <1e71f8880604260844l8a6949ana25cf35c3f4a5c6e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Helo-Milter-Authen: gmc@sonologic.nl, pgsql@metro.cx, mx1 Received-SPF: pass (mx1.sonologic.nl: 213.84.33.240 is authenticated by a trusted mechanism) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/3 X-Sequence-Number: 21535 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.(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.(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/