Is there any way to prevent the resteasy framework from throwing an
"UnhandledException: Response is committed, can't handle exception" when a
client requests a page and disconnects mid-transfer of the file?

My use case is that I'm sending firmware to phones based on some database
lookups, and the firmware can be up to 200MB in size.  If the phone already
has the firmware, it drops the connection after a couple of MB have been
transferred.  Resteasy throws an exception since the client dropped the
session, with the root cause being a ClientAbortException due to a
Connection Reset.

Is it possible to ignore that specific exception, or should I just deal
with the stack traces in the log files?



This document may contain unclassified technical data whose export, 
transfer and/or disclosure is restricted by United States law. 
Dissemination to non-US persons, whether in the United States or abroad may 
require an export license or other authorization. The information contained 
herein, including any attached documents or files, is confidential, may be 
legally privileged and is solely for the intended recipient(s). If you 
received this information in error, please destroy it and notify us 
immediately by reply e-mail, letter, fax or phone. Any unauthorized use, 
dissemination, disclosure, copying or printing is strictly prohibited.
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
Resteasy-users mailing list

Reply via email to