Hi, we upgraded recently to axon 3.2.1, and noticed that now our quartz schedulers within saga are raising errors, like this one:
2018-06-11 11:49:28 ERROR ErrorLogger:2401 - An error occured instantiating job to be executed. job= ‘AxonFramework-Events.event-6df07676-bd92-4470-93d4-9718a1b65242’
org.quartz.SchedulerException: Job instantiation failed [See nested exception: java.lang.IllegalArgumentException: ‘name’ must not be null]
at org.springframework.scheduling.quartz.AdaptableJobFactory.newJob(AdaptableJobFactory.java:47)
at org.quartz.core.JobRunShell.initialize(JobRunShell.java:127)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:392)
Caused by: java.lang.IllegalArgumentException: ‘name’ must not be null
at org.springframework.util.Assert.notNull(Assert.java:193)
at org.springframework.beans.factory.BeanFactoryUtils.transformedBeanName(BeanFactoryUtils.java:74)
at org.springframework.beans.factory.support.AbstractBeanFactory.transformedBeanName(AbstractBeanFactory.java:1117)
at org.springframework.beans.factory.support.AbstractBeanFactory.containsBean(AbstractBeanFactory.java:392)
at org.axonframework.spring.config.AbstractAnnotationHandlerBeanPostProcessor.postProcessAfterInitialization(AbstractAnnotationHandlerBeanPostProcessor.java:66)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:438)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1714)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:414)
at org.springframework.boot.autoconfigure.quartz.AutowireCapableBeanJobFactory.createJobInstance(AutowireCapableBeanJobFactory.java:45)
at org.springframework.scheduling.quartz.AdaptableJobFactory.newJob(AdaptableJobFactory.java:43)
… 2 more
(not so)fun is that we have tests for this sagas with expecting events triggered by quarts, and tests were still green so we were not aware of issues when we tested upgrade
And we did recent upgrade from axon 3.1.2 to be able to use nicer query gateway interface for queries that return multiple results -> meaning that we can’t just go back to 3.1.2 since a lot of code would not compile.
After research, we found that this issue is already solved and scheduled for axon 3.3 release:
https://github.com/AxonFramework/AxonFramework/issues/585
Do you know, is there any workaround/configuration that is possible to allow us to keep going somehow until axon 3.3 is released?
Since this is just research project, there is no urgency in this, it is just question to see what is available, and maybe it also helps someone else as well
Thanks,
Vladimir