From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Stef <svb(at)ucs(dot)co(dot)za> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: An I/O error occured while sending to the backend. |
Date: | 2008-01-11 05:31:41 |
Message-ID: | Pine.BSO.4.64.0801110028010.3943@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Mon, 7 Jan 2008, Stef wrote:
> I'm using the Connection pool manager of JBoss to control
> the connections to the database. When I restart postgres
> without restarting JBoss as well, I get this error reported in JBoss :
> An I/O error occured while sending to the backend.
>
> The problem is that JBoss never recovers from this , and it's only fixed
> when I restart JBoss. I can understand that this error may happen
> occasionally, but I need to be able to recover from this situation
> without restarting JBoss.
>
JBoss has a check-valid-connection-sql parameter for datasources which
runs every time a connection from a pool is allocated. If this statement
fails, the connection is discarded and a new connection is opened. This
should allow recovery from a disappeared database.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Kris Jurka | 2008-01-11 05:33:54 | Re: Deleting LargeObjects as BLOBS |
Previous Message | Kris Jurka | 2008-01-11 05:24:35 | Re: Patch for Statement.getGeneratedKeys() |