Open Closed

Getting Error while fetching tenant by name (mostly after upgrade to 4.4) #1714


User avatar
0
viswajwalith created
  • ABP Framework version: v4.4.X

  • UI type: MVC

  • DB provider: EF Core / MongoDB

  • Tiered (MVC) or Identity Server Separated (Angular): yes (Micro service)

  • Exception message and stack trace: 2021-08-16 18:59:08.897 +00:00 [INF] Request finished HTTP/1.1 GET https://webgateway.XXXXX.com/api/abp/application-configuration?api-version=1.0 - - - 200 204357 application/json;+charset=utf-8 240.2337ms 2021-08-16 18:59:10.300 +00:00 [INF] Request starting HTTP/1.1 GET https://webgateway.XXXXX.com/api/abp/multi-tenancy/tenants/by-name/barik?api-version=1.0 - - 2021-08-16 18:59:10.301 +00:00 [INF] requestId: 8000001b-0003-fc00-b63f-84710c7967bb, previousRequestId: no previous request id, message: EndpointRateLimiting is not enabled for /api/abp/{everything} 2021-08-16 18:59:10.301 +00:00 [INF] requestId: 8000001b-0003-fc00-b63f-84710c7967bb, previousRequestId: no previous request id, message: No authentication needed for /api/abp/multi-tenancy/tenants/by-name/barik 2021-08-16 18:59:10.301 +00:00 [INF] requestId: 8000001b-0003-fc00-b63f-84710c7967bb, previousRequestId: no previous request id, message: /api/abp/{everything} route does not require user to be authorized 2021-08-16 18:59:10.352 +00:00 [WRN] requestId: 8000001b-0003-fc00-b63f-84710c7967bb, previousRequestId: no previous request id, message: 500 (Internal Server Error) status code, request uri: https://administrationservice.dev-ehswatch.com/api/abp/multi-tenancy/tenants/by-name/barik?api-version=1.0 2021-08-16 18:59:10.353 +00:00 [INF] Request finished HTTP/1.1 GET https://webgateway.dev-ehswatch.com/api/abp/multi-tenancy/tenants/by-name/barik?api-version=1.0 - - - 500 343 application/json;+charset=utf-8 52.5521ms

  • Steps to reproduce the issue: we configured the subdomain and url is like tenant.application.com, it used to work fine but we are getting the issue while getting the tenant by name ( ​/api​/abp​/multi-tenancy​/tenants​/by-name​/{name} ) . Mostly we think it is happening after upgrade to 4.4 . can you please help us in getting this solved. this is blocking our prod deployment.

In our webgate way we dont have any entry related to multi-tenancy , are we missing any thing?

FYI... we have updraged from 4.3 to 4.4 manually


4 Answer(s)
  • User Avatar
    0
    viswajwalith created

    It seems the issue is because of using the same RabbitMQ for Dev & QA site, it seems when the distributed event executes and process of user creation for tenant user being picked by service of other environment.

    Do u think we need to have different Rabbit MQ servers for each environment?

  • User Avatar
    0
    yekalkan created
    Support Team Fullstack Developer

    Hi @viswajwalith

    Yes, it is better to have different Rabbit MQ. Otherwise Events will be confused.

    If you must use the same Rabbit MQ, at least you need to use different ExchangeName.

    See https://docs.abp.io/en/abp/latest/Distributed-Event-Bus-RabbitMQ-Integration#configuration

  • User Avatar
    0
    viswajwalith created

    wise Event

    Sure will check and update you

  • User Avatar
    0
    alper created
    Support Team Director

    you can reopen if your issue continues...

Made with ❤️ on ABP v9.1.0-preview. Updated on December 05, 2024, 12:19