You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Complete executable reproducer if available (e.g. GitHub Repo): -
Steps to reproduce
start a app using the Multi-Tenancy Extension connected to a AxonServer
register MultiTenantAwareComponent against the TenantProvider (auto-configured to AxonServerTenantProvider)
cancel that registration
Expected behaviour
All the individual tenant registration from the concerned MultiTenantAwareComponent are cancelled.
No other side-effects:
registrations for other MultiTenantAwareComponent are maintained
connection to Axon Server is maintained for all tenants
Actual behaviour
Registration for all MultiTenantAwareComponent are cancelled on all tenants, not just the concerned MultiTenantAwareComponent.
Connection for all tenants are closed on Axon Server.
Thanks for reporting this issue, based in a quick inspection, it appears this is indeed a bug.
We are already working on a patch that should be released in few weeks so we will include a fix for this issue as well.
I would like to propose a workaround if this is blocking you at the moment, but need more information on use case.
Are you building your own tenant aware component or you want to deregister a existing one?
Removed issue from in progress, lowered the priority, and dropped the milestone 4.9.4 mention.
(1) This issue is currently not in progress, (2) the method is typically not touched at all by a user, (3) and because of the priority, this issue does not merit a 4.9.4 release.
Basic information
Steps to reproduce
MultiTenantAwareComponent
against theTenantProvider
(auto-configured toAxonServerTenantProvider
)Expected behaviour
All the individual tenant registration from the concerned
MultiTenantAwareComponent
are cancelled.No other side-effects:
MultiTenantAwareComponent
are maintainedActual behaviour
Registration for all
MultiTenantAwareComponent
are cancelled on all tenants, not just the concernedMultiTenantAwareComponent
.Connection for all tenants are closed on Axon Server.
See: https://github.com/AxonFramework/extension-multitenancy/blob/main/multitenancy-spring-boot-autoconfigure/src/main/java/org/axonframework/extensions/multitenancy/autoconfig/AxonServerTenantProvider.java#L204-L212
The text was updated successfully, but these errors were encountered: