Troubleshooting multi-tenancy New in 1.14.0
Diagnose Critter Stack multi-tenancy failures: UnknownTenantIdException ('Unknown tenant id'), Fisher's UnknownTenantException, DisabledTenantException, DefaultTenantUsageDisabledException and the sharded/master-table default-tenant refusals, Wolverine.HTTP's 400 'No mandatory tenant id could be detected' and opt-in 404, CrossTenantWriteException, TenantPartitionException, TenantedInboxWriteException, 'Wolverine requires a main message store database', and per-store tenancy admin guards. Covers the four tenant-id casing behaviours across Marten, Wolverine, Polecat and Fisher, why disabled read as unknown before JasperFx 2.74.0, and why none should be retried.
Use when a session, handler or endpoint fails on which tenant it addressed, tenant onboarding partly fails, or mixed-case ids split data.
Skill details
- Skill name:
critterstack-troubleshooting-multi-tenancy - Applies to:
marten,polecat,fisher,wolverine - Tags:
troubleshooting,multi-tenancy,tenants,UnknownTenantIdException,DisabledTenantException,DefaultTenantUsageDisabledException,TenantIdStyle,conjoined,database-per-tenant,master-table,sharded,RequiresTenant,critterwatch,marten,polecat,fisher,wolverine - Added in: 1.14.0
- License: Proprietary. Copyright JasperFx Software LLC.