{"res":X,"msg":"Failed to invoke the method getFaceNotice in the service com.gec.notice.api.INoticeSearchService. Tried 1 times of the providers [X.X.0.X:X] (1/2) from the registry zookeeper1.gmhost:X on the consumer X.X.0.X using the dubbo version 2.5.3. Last error is: Failed to invoke remote method: getFaceNotice, provider: dubbo://X.X.0.X:X/com.gec.notice.api.INoticeSearchService?accepts=X&anyhost=true&application=xcj-issue&check=false&default.check=false&default.delay=X&default.retries=0&default.timeout=X&delay=X&dispatcher=message&dubbo=2.6.2&dump.directory=/data/services/gec-notice/service/logs&generic=false&interface=com.gec.notice.api.INoticeSearchService&methods=getNoticesBySolr,getFaceNoticeDoc,resultCount,getFaceNotice,getHtmlDocument,buildSolrByTime,syncAgain,getExprt,getPlans,getNotice,exchangeAgain,statisByNoticeType,getReNotices,reBuildSolrById,redCount,exchangeDetails,getPlan,getNotices,getNoticesBySolrSimple,getNoticesBySolrSecret,getReadCount,sensitiveScreenTask,countOpenbind,noticeSyncDetails,syncGecNotice,getNoticeSerc,batchSyncNotices,delSomeCashByMsg,financNotice,noticeLinkPlan,revokeSyncGecNotice,noticeReportZH,getNoticeCount,readingCount,getRefers,getNoticesByOffset,modifyingCount,reBuildSolr&pid=X&revision=1.X.X-SNAPSHOT&side=consumer×tamp=X, cause: com.alibaba.dubbo.remoting.ExecutionException: class com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler error when process received event .
com.alibaba.dubbo.remoting.ExecutionException: class com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler error when process received event .
at com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler.received(MessageOnlyChannelHandler.java:X)
at com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:X)
at com.alibaba.dubbo.remoting.transport.MultiMessageHandler.received(MultiMessageHandler.java:X)
at com.alibaba.dubbo.remoting.transport.AbstractPeer.received(AbstractPeer.java:X)
at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.messageReceived(NettyHandler.java:X)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:X)
at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.messageReceived(NettyCodecAdapter.java:X)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:X)
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:X)
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:X)
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:X)
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:X)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:X)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:X)
at java.lang.Thread.run(Thread.java:X)
Caused by: java.util.concurrent.RejectedExecutionException: Thread pool is EXHAUSTED! Thread Name: DubboServerHandler-X.X.0.X:X, Pool Size: X (active: X, core: 0, max: X, largest: X), Task: X (completed: X), Executor status:(isShutdown:false, isTerminated:false, isTerminating:false), in dubbo://X.X.0.X:X!
at com.alibaba.dubbo.common.threadpool.support.AbortPolicyWithReport.rejectedExecution(AbortPolicyWithReport.java:X)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:X)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:X)
at com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler.received(MessageOnlyChannelHandler.java:X)
... X more
","notice":"","refers":"","redcount":0} X