[jira] Issue Comment Edited: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

["Patrick Hunt (JIRA)" <ji...@apache.org>]

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

phunt edited comment on ZOOKEEPER-208 at 11/18/08 1:18 PM:
------------------------------------------------------------------

Great. Thanks much Austin!

I'm marking this as "patch available" on behalf of the author for consideration in 3.1.0.



      was (Author: phunt):
    Great. Thanks much Austin!

I'm marking this as "patch submitted" on behalf of the author for consideration in 3.1.0.


  
> Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active
> --------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-208
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-208
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: c client
>    Affects Versions: 3.0.0
>         Environment: Linux
>            Reporter: Austin Shoemaker
>            Assignee: Austin Shoemaker
>            Priority: Critical
>             Fix For: 3.1.0
>
>         Attachments: zookeeper-strtok_getaddrinfo-trunk.patch, zookeeper-strtok_getaddrinfo-trunk.patch
>
>
> The Zookeeper C client library uses gethostbyname and strtok, both of which are not safe to use from multiple threads.
> The problem is resolved by using getaddrinfo and strtok_r in place of the older API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.