The GitHub Actions job "Run Integration Tests" on rocketmq.git/fix/netty-public-executor-bounded-queue has failed. Run started by GitHub user Aias00 (triggered by Aias00).
Head commit for run: e0f9eae7f45acef2ea85e8ba2ebaaa697fd933f0 / liuhy <[email protected]> [ISSUE #9985] Use CallerRunsPolicy for bounded remoting callback executors The bounded callback executors added for #9985 relied on the default AbortPolicy, so a full queue threw RejectedExecutionException per callback. NettyRemotingAbstract.executeInvokeCallback catches that, logs a WARN-with-stacktrace per rejection, then runs the callback inline on the caller (Netty I/O) thread anyway. Switching to an explicit CallerRunsPolicy keeps the same "run inline under backpressure" outcome without the per-rejection exception and log spam, and satisfies issue #9985's ask for a proper RejectedExecutionHandler. CallerRunsPolicy is already the convention used by the transaction message check listener. Added tests asserting the policy is CallerRunsPolicy and covering the queueCapacity<=0 fallback (previously uncovered per Codecov). Co-Authored-By: Claude <[email protected]> Report URL: https://github.com/apache/rocketmq/actions/runs/31352569692 With regards, GitHub Actions via GitBox
