[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870625#comment-13870625
 ] 

Hudson commented on ZOOKEEPER-1860:
-----------------------------------

SUCCESS: Integrated in ZooKeeper-trunk #2185 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/2185/])
ZOOKEEPER-1860. Async versions of reconfig don't actually throw KeeperException 
nor InterruptedException (Raul Gutierrez Segales via phunt) (phunt: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1557875)
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/src/java/main/org/apache/zookeeper/ZooKeeper.java


> Async versions of reconfig don't actually throw KeeperException nor 
> InterruptedException
> ----------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1860
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1860
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.5.0
>            Reporter: Raul Gutierrez Segales
>            Assignee: Raul Gutierrez Segales
>             Fix For: 3.5.0
>
>         Attachments: ZOOKEEPER-1860.patch
>
>
> This was caught by [~fournc], the async versions of reconfig in the Java 
> client don't actually throw KeeperException nor InterruptedException. Since 
> this is unreleased code (i.e.: for 3.5.0) I don't think there are issues with 
> changing the API (that is, considering what exceptions are thrown part of the 
> API). 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to