Hi,
My bad, the name convention needed the word Async at the end of function names to work.
Thanks for the support
It works correctly, but if I load the application on a page that injects an IApplicationService, when the render mode is Server, it says that it is not registered.
However, if I enter the application through the dashboard and, once the WASM is downloaded, I navigate to the page that has the IAppService, then in Client render mode, it works fine and correctly resolves the dependency injection.
Hello, I created a solution using the command:
abp new Acme.BookStore -u blazor-webapp -m none --theme leptonx -csf
After making changes to BookStoreHttpApiClientModule to use static clients, I ran the command to generate the clients, but I got the following error in the CLI (as shown in the image).
Hi,
I found this open issue on Git Hub
https://github.com/abpframework/abp/issues/10036
Finally I tried to override AzureDistributedEventBus AddToOutboxAync:
using (CurrentTenant.Change(null)) { await eventOutbox.EnqueueAsync(outgoingEventInfo); }
And it works.
Thank you
Sure,
Tenants with database configurations:
In tenant with shared database works fine, event is inserted in AbpEventOutbox an then published to Azure Service Bus and Deleted from AbpEventOutbox:
In tenants with isolated databases, events remain in AbpEventOutbox and aren't published to Azure Service Bus:
My module configuration:
services.Configure<AbpDistributedEventBusOptions>(options =>
{
options.Outboxes.Configure(config =>
{
config.UseDbContext<TDbContext>();
});
options.Inboxes.Configure(config =>
{
config.UseDbContext<TDbContext>();
config.DatabaseName = "ArcoCoreDbContext";
});
});
Hi,
I have been testing with three tenants, two with isolated databases and one tenant with a shared database. I have noticed that when distributed events are generated in the tenants with isolated databases, they are added to the AbpEventOutbox table of those databases. Since there is only one worker for the shared database, these events remain indefinitely in the AbpEventOutbox tables of the isolated databases, causing the messages not to be published to Azure Service Bus.
Best regards.
Hello, It works with the handler.
Now the same issue i had to publish in multiple topics than i have to implement MyAzureDistributedEventBus:AzureDistributedEventBus, i have to implement the receiver/consumer part with inbox pattern, where i need to add to inbox and process messages comming from multiple queues on Azure Service Bus. Is that possible?
Thank you