[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649316#action_12649316 ]
Hudson commented on ZOOKEEPER-208: ---------------------------------- Integrated in ZooKeeper-trunk #149 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/149/]) . Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active. (austin shoemaker, chris daroch and ben reed via mahadev) > 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.0.1, 3.1.0 > > Attachments: ZOOKEEPER-208.patch, > 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.