Activities of "enisn"

ABP has an option for making ExchangeType as Fanout but it applies globally for the application. That means you can make it for all the events, not a particular event.

Configure<AbpRabbitMqEventBusOptions>(options =>{
    options.ExchangeType = ExchangeType.Fanout;
});

You'll need to configure it both published and subscriber applications.

Hi,

It's by design. The event handler is executed only once to prevent concurrent write operations at the same time.

It's the defaults of RabbitMQ. It uses kinda load-balancing operation across the subscribers and sends the event to only one single instance and awaits acknowledge (ACK) info to complete the event. If not, tries to send it again. It's the expected behaviour.

If your intent is for all instances to receive the event (for example, for broadcasting purposes), you’ll need to change the design slightly. A common approach is to use a publish/subscribe pattern with a fanout exchange. In this configuration, each service instance can have its own dedicated queue bound to the fanout exchange. Every time a message is published to the exchange, each bound queue gets its own copy of the message, and thus every instance can process it independently.

ABP Framework doesn't implement this fanout exchange logic since it's coupled to RabbitMQ and ABP uses abstraction over event-buses. That mean, you'll need to implement it on your own by using the RabbitMQ library itself instead using ABP abstractions.

The exception is thrown from there: https://github.com/abpframework/abp/blob/e23e92e8e181a093746d4d5d41e7ef2773a76ea5/framework/src/Volo.Abp.Features/Volo/Abp/Features/FeatureDefinitionManager.cs#L27

It should be get from StaticStore, but it seems there is a missing configuration and it's not defined. Can you make sure your HttpApi.Host project has direct or indirect reference to Volo.Abp.AuditLogging.Application.Contract package? Normally it should.

It seems some files are locked or cannot be accessed. Can you make sure ABP suite or ABP Studio isn't running while trying to open it with abp suite command.

(Windows only) Here what I can suggest if you're not sure which process is working.

taskkill /im dotnet* -f

And then try to execute abp suite command

Is your solution is micro-service template?

You got this log on which database you trying to connect? Which service/application shows this log?

Hi,

AuditLogging.SettingManagement feature is defined in Volo.Abp.AuditLogging.Application.Contracts package. Does your application have reference to that package and also [DependsOf(typeof(AbpAuditLoggingApplicationContractsModule))] attribute over the module class?

If your architecture tiered, some dependnecies might be missing, you can check and add this package and attribute if not exist

Feel free to re-open or create another issue whenever you face an issue while implementing it

It's a strange case. We could reproduce the same problem. It doesn't affect for a while or page-refresh is required to see the it.

I'm creating an internal issue for this and out team will try to figure it out and provide a solution in the framework

Hi,

Our team is working on this topic, we've sent for a report to anti-virus softwares to indicate a false-positive situation but the process isn't completed yet. It seems this is a behavioral situation and not related to a specific code or DLL file. If we have more information about what is the specific action, we might improve that case, but for now we're awaiting response primarily from kaspersky. We do not face ant problems with other anti-virus softwares than kaspersky for now.

Hi @cheelam1220

It's hard to understand the exact problem but based on the information available, the issue described involves a token expiration error. The log indicates a SecurityTokenExpiredException, meaning the token's lifetime validation has failed because it is expired.

Suggested Solutions:

1. Ensure Proper Token Lifetime:

   • Check your token configuration in your authentication server.
   • Verify settings like TokenLifetime in your application settings or wherever the token expiration policy is defined. Extend the token validity duration if necessary.

2. Handle Refresh Tokens:

   • Implement a refresh token mechanism if not already in place. This ensures users can obtain new tokens without needing to re-login when the current token expires.

3. Synchronization of Server Clocks:

   • Check the server's time settings. Differences between the authentication server's clock and the API server's clock can cause this error.

4. Check for Long-Running Requests:

   • Ensure tokens do not expire during long-running API calls. You might need to adjust the token expiration or rethink how long-running tasks are handled.

5. Diagnostics:

   • Add more detailed logging to trace how tokens are being issued and validated.
   • Verify the middleware in your application pipeline (e.g., JwtBearerMiddleware) is correctly handling token validation.

If these steps don't resolve the issue, more details about the token generation and validation process might be necessary to troubleshoot further.