By creating remote case types you provide users of your applications with a tool to process cases related to multiple applications from one context, without logging in and out several times during a work day, because users can create cases that are related to one application in the context of another application. In order for remote case types to work, you first configure a producer system that stores applications with case types, and then you configure a consumer system that hosts the applications that you want to use to process cases at run time. Producer and consumer systems send requests to each other, to pass the data necessary to create remote case types.
Reasons for the alert
The PEGA0132 alert notifies you that a remote request exceeds the client time-out threshold while processing the request. The threshold is 2 seconds. The alert might occur when the consumer system exceeds the threshold when responding to the request, or when fetching a client instance from the client connection pool exceeds the threshold value. The exceeded threshold might have the following reasons:
- The consumer system is unable to handle the request load.
- The response from the producer system is excessively delayed due to network issues or the performance of the producer system.
Example text message
The sample text message is for a uPlusTelco application, and contains details about the client connection pool:
2021-01-27 12:36:49,822 GMT*8*PEGA0132*90*90*fd85ea5f8aab0393a924dc951d794cc0*NA*NA*NA*NA*NA*NA*NA*?*-1*HWNH0UAU4X5BWHWI6ZZ7NC1OZ322DW4DPA*227*NA*NA*com.pega.platform.web.gateway.RemoteWebGatewayImpl*NA*NA*NA*NA*NA*false*GET-cases-12-35-19-275-99**NA*NA*NA*NA*NA*NA*NA*NA*Remote request exceeded threshold time : https://localhost:1080/prweb/app/uPlusTelco/api/application/v2/cases/OPB1HW-uPlusTel-Work-TestCaseType+C-1*, HTTP connection pool stats : [leased: 20; pending: 1; available: 0; max: 20]*
Text messages include the following information:
- Correlation ID, which stores the psync_id data instance of the user that is logged in. The correlation ID is unique for every user session and you can use this data to correlate the alerts from the same user session.
- Client request ID, which you can use to correlate a request in the consumer and producer systems. For requests to the producer system, the format of the request ID is RequestMethod-DxAPIServiceName-Timestamp-UniqueRequestID, where the unique request ID is a series of numbers between 1 and 10000. For requests to the consumer system, the format of the request ID is RequestMethod-DxAPIServiceName-Timestamp-RequestorID.
- KPI threshold, which is the period of time after which the system returns the PEGA0132 alert is the request processing is not complete.
- Actual KPI, which is the actual amount of time that the consumer system took to fetch data from the producer system.
- The client pool details when the reason for the PEGA0132 alert is related to the client pool.
Recommended next steps
To resolve the issue, consider the following actions:
- If the alert is related to consumer system issues with processing requests, configure the consumer system to process heavier loads. You change the load configuration by creating or modifying the gateway/maxconnections dynamic system setting. You can provide a value between 20 and 100 to determine how many concurrent requests the consumer system can process. The default value is 20.
Note: After you save the gateway/maxconnections dynamic system setting, ongoing requests in the system might return the IllegalStateException error. The exception affects only the requests that already exist in the system.
- Contact Global Client Support for help.
For more information, see: