Обсуждение: Intermittent I/O error?

Поиск
Список
Период
Сортировка

Intermittent I/O error?

От
"Vsevolod (Simon) Ilyushchenko"
Дата:
Hi,

I'm getting intermittent infamous errors:

Class: com.romeblack.release.core.EntityHomeException: An I/O error
occured while sending to the backend.
Exception: java.net.SocketException: Socket closed
Stack Trace:
java.net.SocketException: Socket closed
     at java.net.SocketInputStream.socketRead0(Native Method)
     at java.net.SocketInputStream.read(SocketInputStream.java:129)
     at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
     at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
     at org.postgresql.core.PGStream.ReceiveChar(PGStream.java:241)
     at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1122)
     at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
     at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)

These errors don't always occur - sometimes I'm able to run and test the
entire application without ever running into them.

I'm using Tomcat 5.5.9 and JDBC 2 driver 8.0-312 connecting to an 8.0.3
database on Fedora 4.

What can I do to fix this problem?

Thanks,
Simon
--

Simon (Vsevolod ILyushchenko)   simonf@cshl.edu
                http://www.simonf.com

Terrorism is a tactic and so to declare war on terrorism
is equivalent to Roosevelt's declaring war on blitzkrieg.

Zbigniew Brzezinski, U.S. national security advisor, 1977-81

Re: Intermittent I/O error?

От
Oliver Jowett
Дата:
Vsevolod (Simon) Ilyushchenko wrote:

> Class: com.romeblack.release.core.EntityHomeException: An I/O error
> occured while sending to the backend.
> Exception: java.net.SocketException: Socket closed

This means you're trying to use a Connection that has had close() called
on it, or that has encountered a fatal I/O error previously (this would
have been reported via throwing an appropriate SQLException) that you
ignored.

> I'm using Tomcat 5.5.9 and JDBC 2 driver 8.0-312 connecting to an 8.0.3
> database on Fedora 4.

I guess you are using connection pooling then; I'd suspect some problem
there.

-O