咨詢該項(xiàng)目請撥打:400-006-6655
(同時(shí)提供 標(biāo)書代寫、信用評級、
ISO證書辦理、大數(shù)據(jù)等服務(wù))
招標(biāo)代理公司(
立即查看)
受業(yè)主單位(
立即查看)
委托,于
2025-09-16在采購與招標(biāo)網(wǎng)發(fā)布
無人機(jī)LIDAR及配套設(shè)備保險(xiǎn)采購采購公告。現(xiàn)邀請全國供應(yīng)商參與投標(biāo),有意向的單位請及時(shí)聯(lián)系項(xiàng)目聯(lián)系人參與投標(biāo)。
{"res":(略),"msg":"Failed to invoke the method getFaceNotice in the service com.gec.notice.api.INoticeSearchService. Tried 1 times of the providers [(略).(略).0.(略):(略)] (1/2) from the registry zookeeper1.gmhost:(略) on the consumer (略).(略).0.(略) using the dubbo version 2.5.3. Last error is: Failed to invoke remote method: getFaceNotice, provider: dubbo://(略).(略).0.(略):(略)/com.gec.notice.api.INoticeSearchService?accepts=(略)&anyhost=true&application=xcj-issue&check=false&default.check=false&default.delay=(略)&default.retries=0&default.timeout=(略)&delay=(略)&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,exchangeAgain,getNotice,statisByNoticeType,getReNotices,reBuildSolrById,redCount,exchangeDetails,getPlan,getNotices,getNoticesBySolrSimple,getNoticesBySolrSecret,getReadCount,sensitiveScreenTask,noticeSyncDetails,countOpenbind,syncGecNotice,getNoticeSerc,batchSyncNotices,delSomeCashByMsg,financNotice,noticeLinkPlan,revokeSyncGecNotice,noticeReportZH,getNoticeCount,readingCount,getRefers,getNoticesByOffset,modifyingCount,reBuildSolr&pid=(略)&revision=1.(略).7-emergency-SNAPSHOT&side=consumer×tamp=(略), 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:(略))
at com.alibaba.dubbo.remoting.exchange.support.header.HeartbeatHandler.received(HeartbeatHandler.java:(略))
at com.alibaba.dubbo.remoting.transport.MultiMessageHandler.received(MultiMessageHandler.java:(略))
at com.alibaba.dubbo.remoting.transport.AbstractPeer.received(AbstractPeer.java:(略))
at com.alibaba.dubbo.remoting.transport.netty.NettyHandler.messageReceived(NettyHandler.java:(略))
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:(略))
at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.messageReceived(NettyCodecAdapter.java:(略))
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:(略))
at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:(略))
at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:(略))
at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:(略))
at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:(略))
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:(略))
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:(略))
at java.lang.Thread.run(Thread.java:(略))
Caused by: java.util.concurrent.RejectedExecutionException: Thread pool is E(略)HAUSTED! Thread Name: DubboServerHandler-(略).(略).0.(略):(略), Pool Size: (略) (active: (略), core: 0, max: (略), largest: (略)), Task: (略) (completed: (略)), Executor status:(isShutdown:false, isTerminated:false, isTerminating:false), in dubbo://(略).(略).0.(略):(略)!
at com.alibaba.dubbo.common.threadpool.support.AbortPolicyWithReport.rejectedExecution(AbortPolicyWithReport.java:(略))
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:(略))
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:(略))
at com.alibaba.dubbo.remoting.transport.dispatcher.message.MessageOnlyChannelHandler.received(MessageOnlyChannelHandler.java:(略))
... (略) more
","notice":"","refers":"","redcount":0}
(略)查看原文