Re: An I/O error occured while sending to the backend.
| От | Breno BF |
|---|---|
| Тема | Re: An I/O error occured while sending to the backend. |
| Дата | |
| Msg-id | k2qa21be61a1004060801y7cd3db8m3dc666bd39dca8b7@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: An I/O error occured while sending to the backend. (Craig Ringer <craig@postnewspapers.com.au>) |
| Ответы |
Re: An I/O error occured while sending to the backend.
Re: An I/O error occured while sending to the backend. |
| Список | 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
--
- breno bf
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@postnewspapers.com.au>
Breno BF wrote:Further in the exception log, you'll see:
> 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."
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.Turn these down to at least 'info', restart PostgreSQL, and see if you
> log_min_messages = error
> log_min_error_statement = error
get anything informative in the logs.
--
Craig Ringer
--
- breno bf
В списке pgsql-jdbc по дате отправления: