Weird behavior with preStart with UntypedConsumerActor

I have a situation where I have this class

public abstract class ParentConsumerActor extends UntypedConsumerActor {


public class BusinessConsumerActor extends ParentConsumerActor {

  public void preStart() { "preStart run" );

What is weird is when preStart is present in the class, akka doesn’t start-up properly. In particular, when preStart is present in the code the logs indicate the Quartz Scheduler isn’t running, and doesn’t receive any messages via onReceive.


  1. Are there any potential conflicts with using preStart() perhaps in a Spring context? What I’m trying to do is to use preStart() to instantiate some variables on start-up (because I don’t want to change some code downstream in the creation of the actor).

  2. Are there any things I can do to help isolate and debug the problem?

The logs below are missing when preStart is in the code.

2018-10-18 15:56:58, org.quartz.scheduler.jmx.export=true to ensure QuartzScheduler(s) will be enlisted in JMX.
2018-10-18 15:56:58, default implementation for ThreadExecutor
2018-10-18 15:56:58, execution threads will use class loader of thread:
2018-10-18 15:56:58,<init>@@@60@@@Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2018-10-18 15:56:58,<init>@@@229@@@Quartz Scheduler v.1.8.6 created.
2018-10-18 15:56:58, initialized.
2018-10-18 15:56:58, meta-data: Quartz Scheduler (v1.8.6) 'DefaultQuartzScheduler-DomainClusterSystem' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  Currently in standby mode.
  Number of jobs executed: 0
  Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
  Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

2018-10-18 15:56:58, scheduler 'DefaultQuartzScheduler-DomainClusterSystem' initialized from an externally provided properties instance.
2018-10-18 15:56:58, scheduler version: 1.8.6
2018-10-18 15:56:58, Quartz scheduler: DefaultQuartzScheduler-DomainClusterSystem
2018-10-18 15:56:58, DefaultQuartzScheduler-DomainClusterSystem_$_NON_CLUSTERED started.
2018-10-18 15:56:58, trigger: triggerGroup-akka://DomainClusterSystem/user/domain-cmd-consumer-actor.trigger-START-akka://DomainClusterSystem/user/domain-cmd-consumer-actor for action: START on route akka://DomainClusterSystem/user/domain-cmd-consumer-actor
2018-10-18 15:56:58, starting of route akka://DomainClusterSystem/user/domain-cmd-consumer-actor as its configured with autoStartup=false


2018-10-18 15:57:18,217+0000-info-DefaultQuartzScheduler-DomainClusterSystem_Worker-1@@@CachingConnectionFactory@@@initConnection@@@311@@@Established shared JMS Connection: 

Nvm, i think i solved my own problem with

    public void preStart() {