-
-
Notifications
You must be signed in to change notification settings - Fork 141
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
TaskRejectedException Occurance when Submitting Statistics #227
Comments
More detailed exception; Exception
|
I think the task queue is being exhausted here; jhipster-online/src/main/java/io/github/jhipster/online/config/AsyncConfiguration.java Line 67 in ad5439a
@pascalgrimaud @jdubois : Given the large number of stat entries in one particular instance; I wonder if this is some kinda DDOS attack on the stat endpoint? 🤔 |
we should have an api to enable/disable the statistics. It should help us a lot |
@pascalgrimaud would changing to an SimpleAsyncTaskExecutor() be an option? @bean(name = "statisticsExecutor") |
Let me check the code first. I believe this is also used to run the generator, so there might be an impact. |
So someone already fixed the question I had, as we have 2 different task executors, one for the generator, and another one for the stats service. So this is all good to change! |
@jdubois how do you replicate this though to even fix it? |
I don’t know why the task is full: it might not even be our fault, I see in the stats that many people fork and hack the project (typically for internal usage inside their company, which is awesome), and many of those people send us back statistics without understanding what they do (we have lots of stats for options that do not exist …). So it might be one of those users who is DDOS’ing the queue, without any malicious intention. |
It was noticed that the following
TaskRejectedException
occurs from time to time in our production environment. And today (Sep 05th 2020) the number of occurances spiked (around 4,140) for some reason.TaskRejectedException
The text was updated successfully, but these errors were encountered: