TrackKYCTypeUpdate Queue Processor is failing with error: "Request message larger than max message size the server will accept"
Hi All,
We are working on the Pega CLMFS framework.
We are seeing this Queue Process TrackKYCTypeUpdate failing with below error message.
"The request included a message larger than the max message size the server will accept."
|
PEGA0102:w:yedItemsDataFlowService:pega-deploy-batch-6f4d446c9c-4k48x |
|
The Data flow named DelayedItemsDataFlowService encountered an error on node {pega-deploy-batch-6f4d446c9c-4k48x}. The error occurred while processing delayed items for Queue Processor TrackKYCTypeUpdates during the stream service write operation. The exception message is: The request included a message larger than the max message size the server will accept. . |
We already gone through the below link and the solution provided in it not feasible for us.
https://support.pega.com/discussion/solution-kafka-queue-processor-size-issuemaxrequestsize?
How we resolve this issue with optimal solution.
***Edited by Moderator Marije to add Support Case INC-B30172 ***
Accepted Solution
Updated: 9 Aug 2024 10:28 EDT
Pegasystems Inc.
GB
@TariniDash @JAVEDA99 INC-B30172 (Queue Processor fails to process large messages) has been closed with the following solution which is valid for Pega 23.1 versions:
Since you are running Pega 23.1, you need a new set of settings which has been documented in the below document.
Please ensure the read/write permission settings is enabled for the repository.
You confirmed yesterday that you did the changes and it is working fine.
Cognizant Technology Solutions India Ltd.
ES
| INC-B30172 |
Accepted Solution
Updated: 9 Aug 2024 10:28 EDT
Pegasystems Inc.
GB
@TariniDash @JAVEDA99 INC-B30172 (Queue Processor fails to process large messages) has been closed with the following solution which is valid for Pega 23.1 versions:
Since you are running Pega 23.1, you need a new set of settings which has been documented in the below document.
Please ensure the read/write permission settings is enabled for the repository.
You confirmed yesterday that you did the changes and it is working fine.