You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2005/02/22 22:22:27 UTC

DO NOT REPLY [Bug 33700] New: - BlockingBuffer Should Include Cause Exception When Throwing BufferUnderflowException

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: seth@ehawaii.gov


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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org