hi
The InboxProcessor uses distributed locks to prevent messages from being processed multiple times.
That is, there will be only one processor processing the message at a time.
https://github.com/abpframework/abp/blob/rel-10.0/framework/src/Volo.Abp.EventBus/Volo/Abp/EventBus/Distributed/InboxProcessor.cs#L88
The new Failure Retry Policy for InboxProcessor in 10.0:
https://abp.io/docs/10.0/release-info/migration-guides/abp-10-0#failure-retry-policy-for-inboxprocessor
Thanks
hi
What is the purpose of this code?
Have you changed the RequestLocalizationOptions's DefaultRequestCulture?
This error occurs because the DefaultRequestCulture.Culture.Name is null.
Can you share more info?
Thanks
hi
You can remove the role from the claims. After that, in the middleware, you can retrieve all roles for the current user id and set HttpContext.User again.
Thanks.
hi
I have reproduced the 403 error, but the response doesn't contain the error message (The user represented by the token is not allowed to perform the requested action.")
Can you share a test project? liming.ma@volosoft.com
Thanks.
hi
Can you share your test project that has Object reference not set to an instance of an object ?
liming.ma@volosoft.com
I will check and fix it in next suite patch.
Thanks.
hi
How many roles does your current user have? ABP will add all role names to claims(cookies)
Thanks.
I confirmed that it will write the license check error log before exiting.
Thanks.
Great 👍
hi
You can check details here: https://abp.io/docs/latest/suite
Thanks.
hi
Please share the request logs from the logs.txt file.
Thanks.
