Up dev issue#10388

[TigerTurbo]

What is the purpose of the change

fix #10388

Brief changelog

Verifying this change

Checklist

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Add some description to dubbo-website project if you are requesting to add a feature.
• GitHub Actions works fine on your own branch.
• If this contribution is large, please follow the Software Donation Guide.

[codecov-commenter]

Codecov Report

Merging #10414 (2670b6c) into 3.0 (4b55862) will increase coverage by 0.02%.
The diff coverage is 44.82%.

@@             Coverage Diff              @@
##                3.0   #10414      +/-   ##
============================================
+ Coverage     65.66%   65.68%   +0.02%     
+ Complexity      319      295      -24     
============================================
  Files          1234     1238       +4     
  Lines         53916    53940      +24     
  Branches       8155     8155              
============================================
+ Hits          35402    35429      +27     
+ Misses        14664    14657       -7     
- Partials       3850     3854       +4     

Impacted Files	Coverage Δ
...e/dubbo/common/concurrent/DiscardOldestPolicy.java	0.00% <0.00%> (ø)
...pache/dubbo/common/concurrent/RejectException.java	25.00% <25.00%> (ø)
...mmon/threadpool/MemorySafeLinkedBlockingQueue.java	48.27% <53.84%> (+9.38%)	⬆️
...rg/apache/dubbo/common/concurrent/AbortPolicy.java	100.00% <100.00%> (ø)
.../apache/dubbo/common/concurrent/DiscardPolicy.java	100.00% <100.00%> (ø)
...org/apache/dubbo/rpc/protocol/AbstractInvoker.java	66.97% <0.00%> (-3.67%)	⬇️
...he/dubbo/remoting/transport/netty/NettyServer.java	70.17% <0.00%> (-3.51%)	⬇️
...ubbo/common/url/component/param/DynamicValues.java	78.12% <0.00%> (-3.13%)	⬇️
.../registry/zookeeper/ZookeeperServiceDiscovery.java	68.35% <0.00%> (-2.54%)	⬇️
...a/org/apache/dubbo/monitor/dubbo/DubboMonitor.java	88.09% <0.00%> (-2.39%)	⬇️
... and 19 more

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

[AlbumenJ]

why change this line

[AlbumenJ]

MemorySafeLinkedBlockingQueue => Queue would be better?

[TigerTurbo]

if there is no more memory will be throw RejectException

[AlbumenJ]

I mean it's better to change the signature of this function to void reject(E e, Queue<E> queue). The Rejector here should not be coupled with actual queue types like MemorySafeLinkedBlockingQueue.

[AlbumenJ]

How can the user change this field?

[TigerTurbo]

done

[TigerTurbo]

new出来这个队列，再set进去，如下图所示

[AlbumenJ]

I mean it's better to change the signature of this function to void reject(E e, Queue<E> queue). The Rejector here should not be coupled with actual queue types like MemorySafeLinkedBlockingQueue.

[TigerTurbo]

ok