Java Mailing List Archive

http://www.junlu.com/

Home » Home (12/2007) » Apache Tomcat »

EAGAIN

James McIntosh

2006-12-06

Replies:

Hi,

I am having intermittent error message being returned as below and was
wondering if anyone else has come across it and found a cause /
solution / additional info.

java.io.IOException: Exception filling buffer with data from underlying
input stream: not an EAGAIN status, so perhaps disconnected client?

org.apache.coyote.http11.InternalAprInputBuffer.fill (InternalAprInputBuffer.java:824)

I cannot reproduce the error but it is happening on several high volume
sites.

I also found this source change suggestion in the bugzilla and have
noticed that it has not been included in CSV

http://issues.apache.org/bugzilla/show_bug.cgi?id=40960

I have modified it slightly and will be running a test on a live site on
Monday with my changes

if ((-nRead) == Status.ETIMEDOUT || (-nRead) == Status.TIMEUP) {
if ((-nRead) == Status.ETIMEDOUT) {
  System.out.println("Internal APR: ETIMEDOUT");
} else {
  System.out.println("Internal APR: TIMEUP");
}
throw new
java.net.SocketTimeoutException(sm.getString("iib.failedread"));
} else {
  throw new IOException(sm.getString("iib.failedread") + " ERRORCODE:
" + (-nRead));
}

I was want to suggest that a IO exception includes the (-nRead) so that
it is easier to chase down what the exception actually means as
org.apache.tomcat.jni.Status has the Error codes etc.

Kind regards
James McIntosh




---------------------------------------------------------------------
To start a new topic, e-mail: users@(protected)
To unsubscribe, e-mail: users-unsubscribe@(protected)
For additional commands, e-mail: users-help@(protected)

©2008 junlu.com - Jax Systems, LLC, U.S.A.