Actions
Bug #26568
closed
ERROR net.liftweb.actor.ActorLogger - Actor threw an exception
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
Version: 8.3.0~beta2~git202503191041-debian12
Seen at server shutdown time during a server restart triggered by a plugin update :
2025-03-20 06:31:07+0000 INFO policy.generation.manager - Successful policy update '4938' [started 2025-03-20 06:31:05 - ended 2025-03-20 06:31:07]
2025-03-20 06:33:05+0000 ERROR net.liftweb.actor.ActorLogger - Actor threw an exception
net.liftweb.actor.PingerException: StartUpdate could not be scheduled on com.normation.rudder.batch.AbstractScheduler$StatusManager@1ce536b4
at net.liftweb.actor.LAPinger$.schedule(LAPinger.scala:78)
at com.normation.rudder.batch.AbstractScheduler$StatusManager.$anonfun$messageHandler$1(AbstractScheduler.scala:167)
at com.normation.rudder.batch.AbstractScheduler$StatusManager.$anonfun$messageHandler$1$adapted(AbstractScheduler.scala:139)
at scala.PartialFunction$$anonfun$fromFunction$1.applyOrElse(PartialFunction.scala:363)
at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:35)
at net.liftweb.actor.SpecializedLiftActor.execTranslate(LiftActor.scala:338)
at net.liftweb.actor.SpecializedLiftActor.execTranslate$(LiftActor.scala:338)
at com.normation.rudder.batch.AbstractScheduler$StatusManager.execTranslate(AbstractScheduler.scala:112)
at net.liftweb.actor.SpecializedLiftActor.proc2(LiftActor.scala:304)
at net.liftweb.actor.SpecializedLiftActor.$anonfun$processMailbox$1(LiftActor.scala:226)
at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18)
at net.liftweb.actor.SpecializedLiftActor.around(LiftActor.scala:240)
at net.liftweb.actor.SpecializedLiftActor.around$(LiftActor.scala:239)
at com.normation.rudder.batch.AbstractScheduler$StatusManager.around(AbstractScheduler.scala:112)
at net.liftweb.actor.SpecializedLiftActor.processMailbox(LiftActor.scala:226)
at net.liftweb.actor.SpecializedLiftActor.$anonfun$$bang$3(LiftActor.scala:189)
at net.liftweb.actor.LAScheduler$$anon$1$$anon$2.run(LiftActor.scala:76)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@88d0e52[Not completed, task = net.liftweb.actor.LAPinger$$anon$1@cb28b1c] rejected from java.util.conc
urrent.ScheduledThreadPoolExecutor@4d8f8127[Shutting down, pool size = 1, active threads = 0, queued tasks = 4, completed tasks = 42]
at java.base/java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2065)
at java.base/java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:833)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:340)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:579)
at java.base/java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:816)
at net.liftweb.actor.LAPinger$.schedule(LAPinger.scala:76)
... 19 common frames omitted
2025-03-20 06:33:19+0000 INFO application - Rudder starts with PID 9124 on 1 cores
Updated by François ARMAND about 1 month ago
Yeah, we didn't ever find a way to do something about that one.
It's because the threadpool part is quicker than other parts of the app to ack that the app is stopping, so it refuses to accept new scheduling, which cause that exception
Updated by François ARMAND about 1 month ago
- Status changed from New to Rejected
- Target version changed from 8.3.0~rc1 to 8.2.6
Actions