Thanks Robin for reporting this. I could see a jira talking the same. Please have a look at this https://issues.apache.org/jira/browse/ZOOKEEPER-1875
Regards, Rakesh -----Original Message----- From: Robin [mailto:[email protected]] Sent: 21 November 2014 14:00 To: [email protected] Subject: Re:RE: A little bug in org.apache.zookeeper.ZooKeeper (3.4.6) OK, let me try it. 在 2014-11-21 16:17:04，"Flavio Junqueira" <[email protected]> 写道： >Hi Robin, > >Could you create a jira and report it there, please? If you could provide a >patch, even better. > >-Flavio > >-----Original Message----- >From: "Robin" <[email protected]> >Sent: 21/11/2014 07:23 >To: "[email protected]" <[email protected]> >Subject: A little bug in org.apache.zookeeper.ZooKeeper (3.4.6) > >Hi, >In org.apache.zookeeper.ZooKeeper.ZKWatchManager#materialize(), even if the >defaultWatcher is null, it is still be added into the Set and returned. This >would cause a lot of annoying error log at >org.apache.zookeeper.ClientCnxn.EventThread#processEvent as below: > 2014-11-21 15:21:23,279 - ERROR - > [main-EventThread:ClientCnxn$EventThread@524] - Error while calling watcher > java.lang.NullPointerException > at > org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:522) > at > org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:498) > >It can be simply fixed by having a null check in ZKWatchManager. > >Thanks!
