That's what I thought at first, but this happens 80-90% of the time on the 100k+ files. There are two files on the same page, one 100-200k dialog, and a 10-30k sentence.
It seems to me unlikely the users are hitting stop that quickly and that often. These are reasonably fast university connections in a class setting. Could it be another request hitting the server? Mishandling of partial GETs? Related, the catalina Logger doesn't seem to take Filters (or am I missing something?). I'd like to keep this cruft (in the meantime) out of the log. Chris on 9/18/03 3:57 AM, Tim Funk wrote: > Broken pipe means the client the aborted the request which is normal for mp3 > since users probably stop listening to the song early. > > -Tim > > Chris Rolfe wrote: > >> Hi, >> >> My app logs are filled to bursting with stack traces from broken pipes while >> serving embedded mp3 (~100k) files. The files serve ok (status 200), but the >> log clutter is hiding everything else. >> >> Strange thing is these aren't the biggest files. 400k jpg's, etc., no >> problem. The broken pipe exception occurs ONLY on the mp3's. >> >> Any suggestions/clues? >> >> Thanks, >> Chris >> >> Running Tomcat 4.0.4 on an OS X (10.2) setup. >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
