Weird behavior with preStart with UntypedConsumerActor

Akka
1

I have a situation where I have this class

public abstract class ParentConsumerActor extends UntypedConsumerActor {

}

public class BusinessConsumerActor extends ParentConsumerActor {

  public void preStart() {
    log.info( "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.

Question:

  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,452+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@QuartzComponent@@@createSchedulerFactory@@@569@@@Setting org.quartz.scheduler.jmx.export=true to ensure QuartzScheduler(s) will be enlisted in JMX.
2018-10-18 15:56:58,534+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@StdSchedulerFactory@@@instantiate@@@1179@@@Using default implementation for ThreadExecutor
2018-10-18 15:56:58,536+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@SimpleThreadPool@@@initialize@@@270@@@Job execution threads will use class loader of thread: DomainClusterSystem-akka.actor.default-dispatcher-16
2018-10-18 15:56:58,559+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@SchedulerSignalerImpl@@@<init>@@@60@@@Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl
2018-10-18 15:56:58,559+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@QuartzScheduler@@@<init>@@@229@@@Quartz Scheduler v.1.8.6 created.
2018-10-18 15:56:58,561+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@RAMJobStore@@@initialize@@@139@@@RAMJobStore initialized.
2018-10-18 15:56:58,571+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@QuartzScheduler@@@initialize@@@255@@@Scheduler meta-data: Quartz Scheduler (v1.8.6) 'DefaultQuartzScheduler-DomainClusterSystem' with instanceId 'NON_CLUSTERED'
  Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
  NOT STARTED.
  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,571+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@StdSchedulerFactory@@@instantiate@@@1324@@@Quartz scheduler 'DefaultQuartzScheduler-DomainClusterSystem' initialized from an externally provided properties instance.
2018-10-18 15:56:58,572+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@StdSchedulerFactory@@@instantiate@@@1328@@@Quartz scheduler version: 1.8.6
2018-10-18 15:56:58,572+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@QuartzComponent@@@startScheduler@@@403@@@Starting Quartz scheduler: DefaultQuartzScheduler-DomainClusterSystem
2018-10-18 15:56:58,572+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@QuartzScheduler@@@start@@@519@@@Scheduler DefaultQuartzScheduler-DomainClusterSystem_$_NON_CLUSTERED started.
2018-10-18 15:56:58,584+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@ScheduledRoutePolicy@@@scheduleRoute@@@117@@@Scheduled 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,612+0000-info-DomainClusterSystem-akka.actor.default-dispatcher-16@@@DefaultCamelContext@@@doStartOrResumeRouteConsumers@@@3968@@@Skipping 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:
2

Nvm, i think i solved my own problem with

   @Override
    public void preStart() {
        super.preStart();
    }