The dubbo consumer keeps reporting the following error:
This error has no effect on functionality, but repeated error reporting must be resolved.
------------------------------------------------------------------------------------------
2016-10-18 08:34:00.725 [DubboMonitorSendTimer-thread-1] ERROR c.a.dubbo.monitor.dubbo.DubboMonitor - [DUBBO] Unexpected error occur at send statistic, cause: Failed to invoke the method collect in the service com.alibaba.dubbo.monitor.MonitorService. No provider available for the service com.alibaba.dubbo.monitor.MonitorService from registry 192.168.0.45:2181 on the consumer 192.168.0.180 using the dubbo version 2.8.4. Please check if the providers have been started and registered., dubbo version: 2.8.4, current host: 192.168.0.180
com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method collect in the service com.alibaba.dubbo.monitor.MonitorService. No provider available for the service com.alibaba.dubbo.monitor.MonitorService from registry 192.168.0.45:2181 on the consumer 192.168.0.180 using the dubbo version 2.8.4. Please check if the providers have been started and registered.
at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.checkInvokers(AbstractClusterInvoker.java:246) ~[dubbo-2.8.4.jar:2.8.4]
at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:55) ~[dubbo-2.8.4.jar:2.8.4]
at com.alibaba.dubbo.rpc.cluster.support.AbstractClusterInvoker.invoke(AbstractClusterInvoker.java:227) ~[dubbo-2.8.4.jar:2.8.4]
at com.alibaba.dubbo.rpc.cluster.support.wrapper.MockClusterInvoker.invoke(MockClusterInvoker.java:72) ~[dubbo-2.8.4.jar:2.8.4]
at com.alibaba.dubbo.rpc.proxy.InvokerInvocationHandler.invoke(InvokerInvocationHandler.java:52) ~[dubbo-2.8.4.jar:2.8.4]
at com.alibaba.dubbo.common.bytecode.proxy23.collect(proxy23.java) ~[dubbo-2.8.4.jar:2.8.4]
at com.alibaba.dubbo.monitor.dubbo.DubboMonitor.send(DubboMonitor.java:113) ~[dubbo-2.8.4.jar:2.8.4]
at com.alibaba.dubbo.monitor.dubbo.DubboMonitor$1.run(DubboMonitor.java:70) ~[dubbo-2.8.4.jar:2.8.4]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_10]
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) [na:1.7.0_10]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) [na:1.7.0_10]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) [na:1.7.0_10]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.7.0_10]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [na:1.7.0_10]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [na:1.7.0_10]
at java.lang.Thread.run(Thread.java:722) [na:1.7.0_10]
------------------------------------------------------------------------------------------
This is because the monitoring center is not started, but the monitoring address is configured. Start the monitoring center, or remove <dubbo:monitor protocol="registry"> in the xml configuration or dubbo.monitor.protocol=registry in the properties configuration. problem solved.