Why are two tasks submitted to UnorderedThreadPoolEventExecutor's queue ? Even if the previous handler returns, there will still be a task submitted to UnorderedThreadPoolEventExecutor's queue?
See original GitHub issue``Why are two tasks submitted to UnorderedThreadPoolEventExecutor’s queue ? Even if the previous handler returns, there will still be a task submitted to UnorderedThreadPoolEventExecutor’s queue?
This confused me and affected the overload protection of the system. Is there a way to ensure that no task is submitted when the previous handler return?
I would be very grateful if you could reply. ``
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Task queuing in Executors.newFixedThreadPool() - Medium
The answer is (b) the tasks will be submitted as they come and there will be no blocking during the submission of the...
Read more >XTaskQueueCreate - Microsoft Game Development Kit
A task queue has work and completion ports and tasks can be queued to either port. Each port can be configured with its...
Read more >Task Execution with Asio - Packt Hub
The run function blocks until all the handlers in the queue have been dispatched and returns only when the queue is empty. By...
Read more >When would a queue consider a task is completed?
Now, in practice, we would generally use the completion handler with a parameter, perhaps even a Result type:
Read more >Processing streaming data with a thread pool
When a task is submitted to the thread pool, it is placed in the task ... that any tasks submitted when the queue...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@chrisvest @NiteshKant many thx The reason was found. both fireChannelRead & channelReadComplete method of simpleChannelInboundHandler create a task, so i solved it by override channelReadComplete method.
Closing this issue as there was no more details submitted