You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Edward Ribeiro (JIRA)" <ji...@apache.org> on 2013/05/14 15:05:28 UTC

[jira] [Updated] (ZOOKEEPER-1610) Some classes are using == or != to compare Long/String objects instead of .equals()

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward Ribeiro updated ZOOKEEPER-1610:
--------------------------------------

    Affects Version/s: 3.5.0
    
> Some classes are using == or != to compare Long/String objects instead of .equals()
> -----------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-1610
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1610
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client, quorum
>    Affects Versions: 3.5.0, 3.4.5
>            Reporter: Edward Ribeiro
>            Assignee: Edward Ribeiro
>            Priority: Trivial
>         Attachments: ZOOKEEPER-1610.patch
>
>
> The classes org.apache.zookeeper.client.ZooKeeperSaslClient.java and 
> org.apache.zookeeper.server.quorum.flexible.QuorumHierarchical.java compare Strings and/or Longs using referential equality.
> Usually, this is not a problem because the Longs are cached and Strings are interned, but I myself  had problems with those kind of comparisons in the past because one production JVM didn't reused the objects.

--
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