You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Hongchao Deng (JIRA)" <ji...@apache.org> on 2014/09/23 01:18:33 UTC

[jira] [Created] (ZOOKEEPER-2045) ConnectStringParser public api didn't handle null connect string

Hongchao Deng created ZOOKEEPER-2045:
----------------------------------------

             Summary: ConnectStringParser public api didn't handle null connect string
                 Key: ZOOKEEPER-2045
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2045
             Project: ZooKeeper
          Issue Type: Bug
    Affects Versions: 3.5.0
            Reporter: Hongchao Deng
            Assignee: Hongchao Deng
            Priority: Minor
         Attachments: ZOOKEEPER-2045.patch

{code}
public final class ConnectStringParser {
...
   public ConnectStringParser(String connectString) {
   ...
{code}
ConnectStringParser is a public api. Besides that, both ZooKeeper constructor and ZooKeeper#updateServerList used it.

However, it doesn't handle a null connectString. It doesn't help that much to see a NPE showing up. So I add a check to the constructor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)