Project

General

Profile

Actions

Bug #9288

closed

Architecture #2787: Use Doobie or Slick in place of SpringTemplate / squeryl / pur JDBC

Jobs are failling to clean database

Added by Nicolas CHARLES about 8 years ago. Updated about 8 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Maintenance
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Following the migration to doobie, jobs are failing to run database clean, with following error:

2016-10-09 00:03:14] 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@1558cfe1
    at net.liftweb.actor.LAPinger$.schedule(LAPinger.scala:72) ~[lift-actor_2.11-2.6.3.jar:2.6.3]
    at com.normation.rudder.batch.AbstractScheduler$StatusManager$$anonfun$messageHandler$1.applyOrElse(AbstractScheduler.scala:158) ~[classes/:na]
    at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36) ~[na:na]
    at net.liftweb.actor.LiftActor$class.execTranslate(LiftActor.scala:502) ~[lift-actor_2.11-2.6.3.jar:2.6.3]
    at com.normation.rudder.batch.AbstractScheduler$StatusManager.execTranslate(AbstractScheduler.scala:106) [classes/:na]
    at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$proc2(LiftActor.scala:305) [lift-actor_2.11-2.6.3.jar:2.6.3]
    at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply$mcV$sp(LiftActor.scala:227) [lift-actor_2.11-2.6.3.jar:2.6.3]
    at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:227) [lift-actor_2.11-2.6.3.jar:2.6.3]
    at net.liftweb.actor.SpecializedLiftActor$$anonfun$net$liftweb$actor$SpecializedLiftActor$$processMailbox$1.apply(LiftActor.scala:227) [lift-actor_2.11-2.6.3.jar:2.6.3]
    at net.liftweb.actor.SpecializedLiftActor$class.around(LiftActor.scala:241) [lift-actor_2.11-2.6.3.jar:2.6.3]
    at com.normation.rudder.batch.AbstractScheduler$StatusManager.around(AbstractScheduler.scala:106) [classes/:na]
    at net.liftweb.actor.SpecializedLiftActor$class.net$liftweb$actor$SpecializedLiftActor$$processMailbox(LiftActor.scala:226) [lift-actor_2.11-2.6.3.jar:2.6.3]
    at net.liftweb.actor.SpecializedLiftActor$$anonfun$2$$anonfun$apply$mcV$sp$1.apply$mcV$sp(LiftActor.scala:190) [lift-actor_2.11-2.6.3.jar:2.6.3]
    at net.liftweb.actor.LAScheduler$$anonfun$9$$anon$2$$anon$3.run(LiftActor.scala:76) [lift-actor_2.11-2.6.3.jar:2.6.3]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_111]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_111]
    at java.lang.Thread.run(Thread.java:745) [na:1.7.0_111]
Caused by: java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@26196c8c rejected from java.util.concurrent.ScheduledThreadPoolExecutor@4f256ede[Shutting down, pool size = 1, active threads = 0, queued tasks = 10, completed tasks = 26]
    at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2048) ~[na:1.7.0_111]
    at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:821) [na:1.7.0_111]
    at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:325) ~[na:1.7.0_111]
    at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:546) ~[na:1.7.0_111]
    at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:692) ~[na:1.7.0_111]
    at net.liftweb.actor.LAPinger$.schedule(LAPinger.scala:73) ~[lift-actor_2.11-2.6.3.jar:2.6.3]
    ... 16 common frames omitted

Actions

Also available in: Atom PDF