Hi Udara, This is a known bug in Hector. It's a missing null check. But we don't have to worry about it, because this does not impact anything. And this is fixed in next version of Hector. For now, as a workaround you can change the log level. Better to make it FATAL rather than OFF.
Thanks, Bhathiya On Tue, May 13, 2014 at 12:26 PM, Udara Rathnayake <[email protected]> wrote: > Hi all, > > Noticed following error after adding the toolbox deployment feature plus > latest BAM publisher dependencies in to the social framework. I'm using > embedded Cassandra node within ES. > > ERROR {me.prettyprint.cassandra.connection.NodeDiscovery} - Discovery > Service failed attempt to connect CassandraHost > java.lang.NullPointerException > at > me.prettyprint.cassandra.connection.NodeDiscovery.discoverNodes(NodeDiscovery.java:79) > at > me.prettyprint.cassandra.connection.NodeDiscovery.doAddNodes(NodeDiscovery.java:52) > at > me.prettyprint.cassandra.connection.NodeAutoDiscoverService.doAddNodes(NodeAutoDiscoverService.java:45) > at > me.prettyprint.cassandra.connection.NodeAutoDiscoverService$QueryRing.run(NodeAutoDiscoverService.java:51) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) > at > java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > > > Following is my cassandra-component.xml(using default configuration) > > <Cassandra> > <Cluster> > <Name>Test Cluster</Name> > <DefaultPort>9160</DefaultPort> > <!--Nodes>localhost:9160</Nodes--> > <AutoDiscovery disable="true" delay="1000"/> > </Cluster> > </Cassandra> > > After setting following within log4j.properties file as a workaround, now > I dont see this error. > > log4j.category.me.prettyprint.cassandra.connection.NodeDiscovery=OFF > > But how can I actually solve this? What am I missing in my configs? > > Regards, > UdaraR > -- > *Udara Rathnayake* > Software Engineer > WSO2 Inc. : http://wso2.com > > Mobile : +94 772207239 > Twitter : http://twitter.com/udarakr > Blog : http://udarakr.blogspot.com > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Bhathiya Jayasekara* *Software Engineer,* *WSO2 inc., http://wso2.com <http://wso2.com>* *Phone: +94715478185* *LinkedIn: http://www.linkedin.com/in/bhathiyaj <http://www.linkedin.com/in/bhathiyaj>* *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>* *Blog: http://movingaheadblog.blogspot.com <http://movingaheadblog.blogspot.com/>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
