DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33700>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33700 Summary: BlockingBuffer Should Include Cause Exception When Throwing BufferUnderflowException Product: Commons Version: 3.0 Final Platform: PC OS/Version: Windows XP Status: NEW Severity: normal Priority: P2 Component: Collections AssignedTo: commons-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] The code for BlockingBuffer throws BufferUnderflowException when a InterruptedException is thrown. But, the original InterruptedException is not included or wrapped by the new BufferUnderflowException. This makes it difficult to determine if the thread was truly interrupted. I believe the commons project has support for wrapping exception (to support older JVMs). This would be very helpful to support. For instance, line 141 of the 3.0 version of BlockingBuffer. Thanks! -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]