AnsweredAssumed Answered

delaying schedulerFactory startup until bootstrap is complet

Question asked by skoalbrother952 on Aug 31, 2011
Latest reply on Nov 3, 2014 by kaynezhang
We occasionally wipe the store/db when deploying to our QA environment, creating a 'clean' application.

We have a number of quartz jobs that we've configured in a manner as seen in scheduled-jobs-context.xml. 


<bean id="manualPdfUploadTrigger" class="org.alfresco.util.CronTriggerBean" lazy-init="default" autowire="default" dependency-check="default">
  <property name="jobDetail" ref="manualPdfUploadJobDetail" />
- <!–  Once every 30 seconds, continuously
  –>
  <property name="cronExpression" value="0/30 * * * * ?" />
  <property name="scheduler" ref="schedulerFactory" />
  </bean>

The job is trapping a NPE when accessing repository.getCompanyHome().  We are suspecting that the companyHome node is not created yet.

We were hoping that if the repo is being created/refreshed that the scheduler startup would be delayed until after the refresh was completed.  It appears that is not the case.

Maybe we are missing something in our configuration ? 
Is the scheduler startup delayed untl after the bootstrap?

Thanks

ALF enterprise 3.4.2

Outcomes