I just put in a catch for this. If you can let me know if it squashes it would be great!
Jay On Thu, Oct 8, 2015 at 12:19 AM, John B. Clements <cleme...@brinckerhoff.org> wrote: > >> On Oct 6, 2015, at 6:58 AM, Jay McCarthy <jay.mccar...@gmail.com> wrote: >> >> I'm not sure if this answers the question... >> >> These errors are coming from the Web server response-outputing code >> failing when the other side closed the connection early. The exception >> would not be returned to your code, because your code is a function >> from "request -> response" rather than a "request -> void" function >> that ends with a call to "output this response". So, the exception is >> thrown on the Web server's side and will just get caught be the >> connection thread's handler, which just prints it out and cleans up >> for the connection. The only way you could grab this would be to make >> a different dispatcher that called your servlet and then ran its own >> "output this response" code from a context you controlled. >> >> In any case, what would you expect to do with such an exception? The >> connection is gone and you can't do anything about it? > > Honestly, the only thing I’d expect to do with the exception would be to not > print it; I’m capturing stderr from the web-server, and my logs are jammed > with this output. > > John > > > -- Jay McCarthy http://jeapostrophe.github.io "Wherefore, be not weary in well-doing, for ye are laying the foundation of a great work. And out of small things proceedeth that which is great." - D&C 64:33 -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
