-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 10.1
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Multitenancy support
-
Tags:
-
Backlog priority:800
When org.nuxeo.ecm.multi.tenant.MultiTenantServiceImpl#disableTenantIsolationFor is called, the org.nuxeo.ecm.multi.tenant.MultiTenantServiceImpl#unregisterTenant is executed even if a document doesn't exist in the repository.
The latest change in 10.1 of Trash implementation has revealed this issue apparently.
It provokes logs pollution in unit tests:
16:33:29 16:33:29,530 ERROR [EventServiceImpl] Exception during multiTenantListener sync listener execution, continuing to run other listeners 16:33:29 org.nuxeo.ecm.core.api.DocumentNotFoundException: b6e8de0b-a010-43c0-884c-a59c0dfa6dca 16:33:29 at org.nuxeo.ecm.core.storage.sql.coremodel.SQLSession.getDocumentByUUID(SQLSession.java:182) 16:33:29 at org.nuxeo.ecm.core.api.AbstractSession.resolveReference(AbstractSession.java:344) 16:33:29 at org.nuxeo.ecm.core.api.AbstractSession.getCurrentLifeCycleState(AbstractSession.java:2067) 16:33:29 at org.nuxeo.ecm.core.trash.LifeCycleTrashService.isTrashed(LifeCycleTrashService.java:43) 16:33:29 at org.nuxeo.ecm.core.api.AbstractSession.isTrashed(AbstractSession.java:2062) 16:33:29 at org.nuxeo.ecm.core.api.impl.DocumentModelImpl.isTrashed(DocumentModelImpl.java:752) 16:33:29 at org.nuxeo.ecm.multi.tenant.MultiTenantServiceImpl.getTenantIdForTenant(MultiTenantServiceImpl.java:220) 16:33:29 at org.nuxeo.ecm.multi.tenant.MultiTenantServiceImpl.lambda$unregisterTenant$1(MultiTenantServiceImpl.java:205) 16:33:29 at org.nuxeo.runtime.api.Framework.doPrivileged(Framework.java:260) 16:33:29 at org.nuxeo.ecm.multi.tenant.MultiTenantServiceImpl.unregisterTenant(MultiTenantServiceImpl.java:205) 16:33:29 at org.nuxeo.ecm.multi.tenant.MultiTenantServiceImpl.disableTenantIsolationFor(MultiTenantServiceImpl.java:182)
It's polluting a lot the NBM unit tests too of course.
