"Caldarale, Charles R" <chuck.caldar...@unisys.com> wrote: >> From: Mark Thomas [mailto:ma...@apache.org] >> Subject: Strange APR/native behaviour > >> The problem I am seeing is with a non-blocking write in the >> AprServletOutputStream [1]. > >> If a write returns EAGAIN (line 97) the socket is added to the poller >> for write notifications. The poller immediately returns the socket as >> ready for write. Another write is attempted that returns EAGAIN and >the >> code enters an infinite loop with no more data ever written to the >socket. > >> If I add a delay around line 46 that slows the rate of writing down, >> EAGAIN is never returned and the test completes successfully. > >Are you positive the EAGAIN path is being taken? Or could it be an >exception is being thrown (and swallowed), leaving result = 0, thereby >adding the socket to the poller at line 93 and returning zero? > > - Chuck
Yes, I am positive. I was using a debugger and had a break point in the EAGAIN path. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
