Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the Questions about "was not accepted before close" #15

Closed
catkins10 opened this issue May 5, 2018 · 1 comment
Closed

the Questions about "was not accepted before close" #15

catkins10 opened this issue May 5, 2018 · 1 comment

Comments

@catkins10
Copy link

Define 300 tasks to be added to EventGroup. The task type is CONCURRENT. After executing close, the task is discarded directly. Warning message: "Handler in newHandlerQueue was not accepted before close net.openhft.chronicle.threads"!

Cause Analysis:
When the task is added to VanillaEventLoop and EventGroup.close() is executed, the task in newHandlerQueue is discarded directly. This is not logical!
Tasks added before close should be executed!
Isn't it waiting for the task in newHandlerQueue to complete and shutting down VanillaEventLoop?

If it is the current logic, I think its use scenario is almost non-existent. If the scenario is limited, where does the high performance performance not be realized?

@dpisklov
Copy link
Contributor

dpisklov commented May 9, 2018

This is expected behaviour and in line with ExecutorService#shutdownNow()
Once again, please use stackoverflow for questions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants