[ 
https://issues.apache.org/jira/browse/SYNCOPE-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742019#comment-17742019
 ] 

ASF subversion and git services commented on SYNCOPE-1770:
----------------------------------------------------------

Commit 73de3cf3eb6f8bbe9b651a1ef578ff2f2be16a3d in syncope's branch 
refs/heads/3_0_X from Francesco Chicchiriccò
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=73de3cf3eb ]

[SYNCOPE-1770] Fixing various quirks with Domains (#490)



> Errors upon Core restart after adding domain
> --------------------------------------------
>
>                 Key: SYNCOPE-1770
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-1770
>             Project: Syncope
>          Issue Type: Bug
>          Components: console, core
>    Affects Versions: 3.0.4
>            Reporter: Francesco Chicchiriccò
>            Assignee: Francesco Chicchiriccò
>            Priority: Major
>              Labels: multitenancy
>             Fix For: 3.0.5, 4.0.0
>
>
> When, after adding a secondary, the Core is restarted, there are error 
> conditions related to the additional Spring beans defined.
> {code}
> java.lang.NullPointerException: Cannot invoke 
> "org.springframework.beans.factory.support.DefaultListableBeanFactory.containsBeanDefinition(String)"
>  because the return value of 
> "org.apache.syncope.core.spring.ApplicationContextProvider.getBeanFactory()" 
> is null
>     at 
> org.apache.syncope.core.persistence.jpa.DomainConfFactory.unregisterBeanDefinition(DomainConfFactory.java:64)
>     at 
> org.apache.syncope.core.persistence.jpa.DomainConfFactory.registerBeanDefinition(DomainConfFactory.java:70)
>     at 
> org.apache.syncope.core.persistence.jpa.DomainConfFactory.register(DomainConfFactory.java:93)
>     at 
> org.apache.syncope.core.persistence.jpa.RuntimeDomainLoader.added(RuntimeDomainLoader.java:60)
>     at 
> org.apache.syncope.common.keymaster.client.zookeeper.ZookeeperDomainOps.lambda$afterPropertiesSet$0(ZookeeperDomainOps.java:73)
>     at 
> org.apache.curator.framework.recipes.cache.CuratorCacheImpl.lambda$putStorage$6(CuratorCacheImpl.java:288)
>     at 
> org.apache.curator.framework.listen.MappingListenerManager.lambda$forEach$0(MappingListenerManager.java:93)
>     at 
> org.apache.curator.framework.listen.MappingListenerManager.forEach(MappingListenerManager.java:90)
>     at 
> org.apache.curator.framework.listen.StandardListenerManager.forEach(StandardListenerManager.java:90)
>     at 
> org.apache.curator.framework.recipes.cache.CuratorCacheImpl.lambda$callListeners$9(CuratorCacheImpl.java:302)
>     at 
> java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804)
>     at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
>     at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
>     at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
> {code}
> Parameter 0 of method transactionTemplate in 
> org.springframework.boot.autoconfigure.transaction.TransactionAutoConfiguration$TransactionTemplateConfiguration
>  required a single bean, but 2 were found:
>     - MasterTransactionManager: defined by method 'transactionManager' in 
> class path resource 
> [org/apache/syncope/core/persistence/jpa/MasterDomain.class]
>     - newDomainTransactionManager: defined in unknown location
> {code}
> Also, Console Dashboard is always showing numbers for {{Master}} domain.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to