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

Hudson commented on ZOOKEEPER-1493:
-----------------------------------

Integrated in ZooKeeper-trunk #1628 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/1628/])
    ZOOKEEPER-1493. C Client: zookeeper_process doesn't invoke completion 
callback if zookeeper_close has been called (Michi Mutsuzaki via phunt and 
mahadev) (Revision 1366784)

     Result = SUCCESS
phunt : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1366784
Files : 
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/src/c/src/zookeeper.c

                
> C Client: zookeeper_process doesn't invoke completion callback if 
> zookeeper_close has been called
> -------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1493
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1493
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.4.3, 3.3.5
>            Reporter: Michi Mutsuzaki
>            Assignee: Michi Mutsuzaki
>             Fix For: 3.3.6, 3.4.4, 3.5.0
>
>         Attachments: ZOOKEEPER-1493.patch, ZOOKEEPER-1493_3_3.patch, 
> ZOOKEEPER-1493_3_4.patch
>
>
> In ZOOKEEPER-804, we added a check in zookeeper_process() to see if 
> zookeeper_close() has been called. This was to avoid calling assert(cptr) on 
> a NULL pointer, as dequeue_completion() returns NULL if the sent_requests 
> queue has been cleared by free_completion() from zookeeper_close(). However, 
> we should still call the completion if it is not NULL. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to