You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (Jira)" <ji...@apache.org> on 2021/09/28 10:20:00 UTC

[jira] [Created] (SYNCOPE-1644) Task run failure with multi-node deployments

Francesco Chicchiriccò created SYNCOPE-1644:
-----------------------------------------------

             Summary: Task run failure with multi-node deployments
                 Key: SYNCOPE-1644
                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1644
             Project: Syncope
          Issue Type: Bug
          Components: core
    Affects Versions: 2.1.9
            Reporter: Francesco Chicchiriccò
            Assignee: Francesco Chicchiriccò
             Fix For: 2.1.10, 3.0.0


Under certain conditions:

* multi-node deployment
* LB in front
* task or report created and executed by two subsequent calls to LB, reaching two different back-end nodes (typically from Console)

an error is raised:

{code}
org.quartz.SchedulerException: Job instantiation failed [See nested exception: org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'taskJob379a7e29-e7cf-4373-9a7e-29e7cfa373b6' available]
{code}

This happens because [AutowiringSpringBeanJobFactory|https://github.com/apache/syncope/blob/syncope-2.1.9/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/AutowiringSpringBeanJobFactory.java] is expecting a singleton bean for each task or report to run: such a bean is registered upon task or report create, but remains in memory only for the node on which create has happened.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)