Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 62153 invoked from network); 16 Jun 2005 12:17:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Jun 2005 12:17:07 -0000 Received: (qmail 89628 invoked by uid 500); 16 Jun 2005 12:17:03 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 89590 invoked by uid 500); 16 Jun 2005 12:17:02 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 89576 invoked by uid 99); 16 Jun 2005 12:17:02 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of pitosalas@gmail.com designates 64.233.170.196 as permitted sender) Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.196) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 16 Jun 2005 05:17:02 -0700 Received: by rproxy.gmail.com with SMTP id i8so293835rne for ; Thu, 16 Jun 2005 05:16:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=kbZBDCuRybuS169daRv3CMYLOc/lHrCMqROVSxBojF2+oG9UfmIchw6SnyCwf7T5EThp/SJ+SwMv1355+zG1NE59V+bj0EucBOFKKfhNmqnjxe8lBXdFcgAspBHgYd+c68LEOEbsHt1eclPP5jRJs3y1sZ+xSgmXKl0dT9tuZDk= Received: by 10.38.181.17 with SMTP id d17mr524900rnf; Thu, 16 Jun 2005 05:16:47 -0700 (PDT) Received: from ?192.168.1.118? ([66.30.198.144]) by mx.gmail.com with ESMTP id a29sm904705rng.2005.06.16.05.16.46; Thu, 16 Jun 2005 05:16:47 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v730) References: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <79AA4D91-79BE-4B36-96F0-0826C88B4168@gmail.com> Content-Transfer-Encoding: 7bit From: Pito Salas Subject: [collections] commons.collections.buffer.BlockingBuffer throws BufferUnderflowException Date: Thu, 16 Jun 2005 08:16:33 -0400 To: commons-dev@jakarta.apache.org X-Mailer: Apple Mail (2.730) X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N commons.collections.buffer.BlockingBuffer throws BufferUnderflowException Why does that make sense? I would think that a BlockingBuffer cannot underflow on a get(). Looking at the code for get() I see: public Object get() { synchronized (lock) { while (collection.isEmpty()) { try { wait(); } catch (InterruptedException e) { throw new BufferUnderflowException(); } } return getBuffer().get(); } } So, an InterruptedException is turned into a BufferUnderflowException. Usually InterruptedException is just re-thrown. I don't understand how to interpret the conversion to a BufferUnderflowException, and whether I can / should safely ignore it. Anyone? Pito --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org