-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
eureka-client-1.4.12 TimedSupervisorTask : task supervisor rejected the task #907
Comments
Do I need to set the parameters when I use? |
Hi @rqw I believe some fixes for this has gone into the later eureka releases. I see that spring cloud netflix currently has an 1.3.* RC release out that has upgraded to the latest eureka client. |
Hi @qiangdavidliu ,Thank you for your answer. |
Same issue here and using the latest from Spring Cloud. I have one Eureka server and two microservices, with one upstream from the other. When I use RestTemplate to call the other microservice, I get the same error referenced by spring-cloud/spring-cloud-netflix#1060 |
Same problem as @ericis and no news about the solution, thanks. Only change the log level? |
@troshko111 pls let us know why this ticket was closed. I still see a similar issue in euraka-client-1.6.2 Waiting for response. Thanks! |
@AmarRocks the issue was closed as stale (2yo), if you experience this on the latest version please reopen with a minimal repro, (note that |
We got the same warning on a prod environment. we are using spring cloud 2020.0.4 (eureka-client-1.10.16). the warnings only disappeared after the service was restarted. |
Hi, anyone who found a solution to this problem. Everyday after midnight my services do down because of this issues. Using: 2022-07-18 23:06:27.629 INFO 52267 --- [trap-executor-0] c.n.d.s.r.aws.ConfigClusterResolver : Resolving eureka endpoints via configuration |
Spring Cloud Version: 2020.0.5 Hi Team,same issue as mentioned by @intumba ,every night my gateway service goes down with below stack-trace.Has anyone found any solution yet. |
Hi @EnnBi hope this will help you too. I resolved it by controlling it through Docker, setup my Docker container to force start whenever the service goes down. That way the service is always available. |
I'm getting the same issue has well. Is it just a bunch of warnings, or does it affect your application? Or your get warnings first, and eventually your application shuts down? |
@ranban282 I have updated my spring cloud version and boot version.And issue got resolved |
What versions are you using? |
Spring-Boot: 2.6.6 |
Source TimedSupervisorTask.java line 62
Need to determine whether the executor is shutdown.
Specific is when using spring cloud eurekaClient.
exception stack:
`
2017-03-04 11:47:34.485 ERROR 21604 --- [ver-bootstrap-0] c.netflix.discovery.TimedSupervisorTask : task supervisor rejected the task
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@300f48c6 rejected from java.util.concurrent.ThreadPoolExecutor@3ec8a0b7[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) ~[na:1.8.0_92]
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) [na:1.8.0_92]
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) [na:1.8.0_92]
at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) ~[na:1.8.0_92]
at com.netflix.discovery.TimedSupervisorTask.run(TimedSupervisorTask.java:62) ~[eureka-client-1.4.12.jar:1.4.12]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [na:1.8.0_92]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_92]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) [na:1.8.0_92]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.8.0_92]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [na:1.8.0_92]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [na:1.8.0_92]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_92]
`
The text was updated successfully, but these errors were encountered: