AllKai commented on issue #14675:
URL: https://github.com/apache/dubbo/issues/14675#issuecomment-2412694881

   > `2024-10-15T10:37:20.842+08:00 WARN 1 --- [d-engine] [ientWorker-16-1] 
r.p.t.t.TripleHttp2ClientResponseHandler : [DUBBO] Meet Exception on 
ClientResponseHandler, status code is: INTERNAL, dubbo version: 3.3.1, current 
host: 10.224.202.60, error code: 4-10. This may be caused by , go to 
https://dubbo.apache.org/faq/4/10 to find instructions. 
java.util.concurrent.RejectedExecutionException: null at 
org.apache.dubbo.common.threadpool.ThreadlessExecutor.execute(ThreadlessExecutor.java:101)
 ~[dubbo-3.3.1.jar!/:3.3.1] at 
org.apache.dubbo.common.threadpool.serial.SerializingExecutor.schedule(SerializingExecutor.java:73)
 ~[dubbo-3.3.1.jar!/:3.3.1] at 
org.apache.dubbo.common.threadpool.serial.SerializingExecutor.execute(SerializingExecutor.java:65)
 ~[dubbo-3.3.1.jar!/:3.3.1] at 
org.apache.dubbo.rpc.protocol.tri.stream.AbstractTripleClientStream$ClientTransportListener.onClose(AbstractTripleClientStream.java:459)
 ~[dubbo-3.3.1.jar!/:3.3.1] at org.apache.dubbo.rpc.protocol.tri.transport.T
 
ripleHttp2ClientResponseHandler.channelInactive(TripleHttp2ClientResponseHandler.java:83)
 ~[dubbo-3.3.1.jar!/:3.3.1] at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:303)
 ~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:281)
 ~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:274)
 ~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1402)
 ~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:301)
 ~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.channel.AbstractChannelHandlerContext.invokeChannelI
 nactive(AbstractChannelHandlerContext.java:281) 
~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:900)
 ~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.handler.codec.http2.AbstractHttp2StreamChannel$Http2ChannelUnsafe$2.run(AbstractHttp2StreamChannel.java:797)
 ~[netty-codec-http2-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
 ~[netty-common-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
 ~[netty-common-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:469)
 ~[netty-common-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:566) 
~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] at io.netty.util.c
 oncurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:994) 
~[netty-common-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) 
~[netty-common-4.1.112.Final.jar!/:4.1.112.Final] at 
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
 ~[netty-common-4.1.112.Final.jar!/:4.1.112.Final] at 
java.base/java.lang.Thread.run(Thread.java:1583) ~[na:na] `
   
   <img width="1288" alt="image" 
src="https://github.com/user-attachments/assets/f37e668a-643c-48ae-bce7-f8dd47470b6c";>
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to