You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue involves a 504 Gateway Timeout error when retrieving APIs subscribed by a specific application through a REST API call. This issue occurs when listing an application with over 100 API subscriptions. The logs revealed that the processing time for the call exceeded 4 minutes before the error occurred.
...
There is/are [26] thread(s) in total that are monitored by this Valve and may be stuck., tenantDomain=carbon.super, correlation-id= java.lang.Throwable
at org.wso2.carbon.user.core.authorization.PermissionTree.updatePermissionTree(PermissionTree.java:1004)
at org.wso2.carbon.user.core.authorization.PermissionTree.updatePermissionTree(PermissionTree.java:962)
at org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.isUserAuthorized(JDBCAuthorizationManager.java:276)
...
This issue occurs when listing an application with over 100 API subscriptions. The logs revealed that the processing time for the call exceeded 4 minutes before the error occurred. It was identified that for each API in the subscription list, the following call is made to the database.
In addition to the above, a call to update the permission tree (updatePermissionTree()) is being made for each .rxt resource. So, if there are 5 APIs, then the updatePermissionTree() method would get called for each resource related to each API ["provider.rxt", "api.rxt", "productdocument.rxt", "documentation.rxt", "product.rxt"].
When listing the APIs subscribed to an application, and if that application has a high number of APIs, this would make DB calls based on the number of resources and also the number of APIs. As observed for the customer, with all the calls accumulated, a timeout error would get thrown in such scenarios.
Steps to Reproduce
N/A
Affected Component
Analytics
Version
APIM 4.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered:
Description
This issue involves a 504 Gateway Timeout error when retrieving APIs subscribed by a specific application through a REST API call. This issue occurs when listing an application with over 100 API subscriptions. The logs revealed that the processing time for the call exceeded 4 minutes before the error occurred.
This issue occurs when listing an application with over 100 API subscriptions. The logs revealed that the processing time for the call exceeded 4 minutes before the error occurred. It was identified that for each API in the subscription list, the following call is made to the database.
In addition to the above, a call to update the permission tree (updatePermissionTree()) is being made for each .rxt resource. So, if there are 5 APIs, then the updatePermissionTree() method would get called for each resource related to each API ["provider.rxt", "api.rxt", "productdocument.rxt", "documentation.rxt", "product.rxt"].
When listing the APIs subscribed to an application, and if that application has a high number of APIs, this would make DB calls based on the number of resources and also the number of APIs. As observed for the customer, with all the calls accumulated, a timeout error would get thrown in such scenarios.
Steps to Reproduce
N/A
Affected Component
Analytics
Version
APIM 4.2.0
Environment Details (with versions)
No response
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: