You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Thawan Kooburat (JIRA)" <ji...@apache.org> on 2013/02/01 04:13:13 UTC

[jira] [Commented] (ZOOKEEPER-1636) c-client crash when zoo_amulti failed

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

Thawan Kooburat commented on ZOOKEEPER-1636:
--------------------------------------------

[~marshall] Do you have any comment on this patch? Seem to relate to multi and memory leak a bit. 
                
> c-client crash when zoo_amulti failed 
> --------------------------------------
>
>                 Key: ZOOKEEPER-1636
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1636
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.4.3
>            Reporter: Thawan Kooburat
>            Assignee: Thawan Kooburat
>            Priority: Critical
>         Attachments: ZOOKEEPER-1636.patch, ZOOKEEPER-1636.patch
>
>
> deserialize_response for multi operation don't handle the case where the server fail to send back response. (Eg. when multi packet is too large) 
> c-client will try to process completion of all sub-request as if the operation is successful and will eventually cause SIGSEGV

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira