From: | Breno BF <brenobfernandes(at)bsd(dot)com(dot)br> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: An I/O error occured while sending to the backend. |
Date: | 2010-04-06 15:01:11 |
Message-ID: | k2qa21be61a1004060801y7cd3db8m3dc666bd39dca8b7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi,
Craig, since I changed it to info, I could not see nothing in postgres logs
when the problem occurs.
log_min_messages = info
log_min_error_statement = info
should I change it to debug?
-B
2010/4/6 Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
> Breno BF wrote:
>
> > I am getting this error using glassfish and postgresql: " Caused by:
> > org.postgresql.util.PSQLException: An I/O error occured while sending to
> > the backend."
>
> Further in the exception log, you'll see:
>
> Caused by: java.net.SocketException: Socket closed
>
> In other words, the pgsql backend has "hung up" on the client. Most
> likely the Pg backend terminated for some reason, which you should see
> in the PostgreSQL logs.
>
> > log_min_messages = error
> > log_min_error_statement = error
>
> Turn these down to at least 'info', restart PostgreSQL, and see if you
> get anything informative in the logs.
>
> --
> Craig Ringer
>
--
- breno bf
From | Date | Subject | |
---|---|---|---|
Next Message | Breno BF | 2010-04-07 10:58:33 | Re: An I/O error occured while sending to the backend. |
Previous Message | Oliver Jowett | 2010-04-06 05:52:18 | Re: Statement.cancel() doesn't seem to work |