Unable to create tenant after adding the ABPEventbus package and pointing Azure Service Bus #10459

1 Answer(s)

• 

  0

  AI-Bot created 3 hours ago

  Support Team ABP Agent

  • What you’re seeing is expected when you enable Azure Service Bus as ABP’s distributed event bus: ABP’s built-in modules (Identity/TenantManagement/SaaS, etc.) also publish integration events (e.g., user/tenant created). After you add Volo.Abp.EventBus.Azure / AbpEventBusAzureModule, those events are no longer “in-memory”; they are sent to Azure Service Bus.
  • If your seeding / tenant provisioning flow (or any custom logic) assumes “publish + handle immediately in the same process”, it will break because distributed events are asynchronous and handled by subscribers via the broker.

  Solution

  1. Enable Outbox/Inbox for transactional reliability (recommended)

     • Configure Outbox/Inbox so events are persisted in the DB within the same Unit Of Work and published safely after commit (and consumers are idempotent).
     • This prevents “seed happened but handler didn’t see it” / timing issues and is the official pattern for transactional distributed events.

  2. Do not rely on distributed event handlers for “must-run-now” seeding logic

     • Anything required to complete tenant creation (like creating admin user, initial roles, settings, etc.) should run directly in the tenant creation workflow (application service / domain service), not via IDistributedEventHandler<>.
     • Use distributed events only for eventual side effects (notifications, integrations, async processes).

  3. If only one app should use Azure Service Bus, disable it in the others

     • In tiered solutions (HttpApi.Host, Web, etc.) you can end up with multiple apps trying to publish/consume. If your scenario is like “only my Notification module should use ASB”, but you enabled it globally, it impacts Identity/Tenant flows too.
     • Apply the approach used in ABP support: disable service bus in the module/app where you don’t want it active (so those apps keep behaving as before).

  Verified references

  • ABP docs: Outbox/Inbox for transactional distributed events (reliability + consistency): https://abp.io/docs/latest/framework/infrastructure/event-bus/distributed#outbox-inbox-for-transactional-events
  • ABP docs: Azure Service Bus distributed event bus: https://abp.io/docs/latest/framework/infrastructure/event-bus/distributed/azure
  • ABP support case mentioning disabling Azure Service Bus in a host app (IsServiceBusDisabled = true): https://abp.io/support/questions/6222

  ---

  This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.

  Save Cancel