Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
Received-SPF: pass (athena.apache.org: domain of yuzhihong@gmail.com
 designates 209.85.215.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CALte62zN-WejkJVcMTu=4c4=TjXuXRsFKimHB-6z1Xp7YWFOrw@mail.gmail.com>
References: 
 <CAL5zq9a3Y+szSbr7qvHh2=dvQf7gwnbWn3m0As4COwJ=eiS8dg@mail.gmail.com>
	<CALte62zN-WejkJVcMTu=4c4=TjXuXRsFKimHB-6z1Xp7YWFOrw@mail.gmail.com>
Date: Fri, 1 Nov 2013 15:42:01 -0700
Message-ID: 
 <CALte62yezdb160PCEXiF3M7_dKUyZuJAtJE+NFBkb47OGa+QsA@mail.gmail.com>
Subject: Re: InterruptedException handling
From: Ted Yu <yuzhihong@gmail.com>
To: dev@accumulo.apache.org
Content-Type: multipart/alternative; boundary=089e0158c0045684dc04ea2546de

--089e0158c0045684dc04ea2546de
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable

Luckily Google comes to the rescue:

http://webcache.googleusercontent.com/search?q=3Dcache:940mX01ckwMJ:www.ibm=
.com/developerworks/java/library/j-jtp05236/index.html%3Fiframe%3Dtrue%26wi=
dth%3D80%25%26height%3D80%25+&cd=3D1&hl=3Den&ct=3Dclnk&gl=3Dus


On Fri, Nov 1, 2013 at 3:39 PM, Ted Yu <yuzhihong@gmail.com> wrote:

> In code reviews, I referred to the following article (I believe is the
> same as the Chinese version) which isn't there anymore:
> http://www.ibm.com/developerworks/java/library/j-jtp05236/index.html
>
> The following search returned nothing:
>
>
> http://www.ibm.com/developerworks/java/library/?sort_by=3D&show_abstract=
=3Dtrue&show_all=3D&search_flag=3D&contentarea_by=3DJava+technology&search_=
by=3DInterruptedException&topic_by=3D-1&industry_by=3D-1&type_by=3DAll+Type=
s&ibm-search=3DSearch
>
> However, code speaks by itself. I often refer people to:
> =C7=E5=B5=A5 3. =B2=B6=D7=BD InterruptedException =BA=F3=BB=D6=B8=B4=D6=
=D0=B6=CF=D7=B4=CC=AC
> which says "restore interrupt status after catchingInterruptedException"
>
> Cheers
>
>
> On Fri, Nov 1, 2013 at 3:31 PM, Christopher <ctubbsii@apache.org> wrote:
>
>> It was pointed out to me by a colleague that we're not properly
>> handling InterruptedException in many places.
>>
>> He cited this article (I could only find it in Chinese, but Google
>> Translate works quite well converting it to English):
>> http://www.ibm.com/developerworks/cn/java/j-jtp05236.html
>>
>> One place we do this a lot is UtilWaitThread. Should we be concerned
>> about this? How do we want to address it?
>>
>> (Also, does anybody have a link to the English version of that article?)
>>
>> --
>> Christopher L Tubbs II
>> http://gravatar.com/ctubbsii
>>
>
>

--089e0158c0045684dc04ea2546de--