Introduction
Issue: Access Platform Config Client - RESOURCE_EXHAUSTED Error
You may encounter the following error in the application logs, which indicates that a gRPC message being processed by the Access Platform Config Client has exceeded the maximum allowable size:
2025-10-06T19:20:29.798Z [jfrt ] [ERROR] [ ] [j.a.c.g.GrpcStreamObserver:131] [default-executor-864] - Access Platform Config Client 1 - unexpected error (status: Status{code=RESOURCE_EXHAUSTED, description=gRPC message exceeds maximum size 4194304: 6200677, cause=null})
Explanation
The error status RESOURCE_EXHAUSTED means a resource has been consumed, usually by hitting a limit. In this case, the limit is the maximum gRPC inbound message size set on the server or client configuration.
- Default Limit: The log shows the current maximum size is 4194304 bytes (which is 4 MiB).
- Actual Message Size: The log shows the message size was 6200677 bytes (approximately 5.9 MiB), exceeding the 4 MiB limit.
This often happens when a configuration object, list of items, or payload being sent via gRPC has grown larger than the system's default or configured cap.
Solution: Increase maxInboundMessageSize
To resolve this, you need to increase the maxInboundMessageSize setting in your application's system.yaml configuration file to accommodate the larger messages.
- Locate the system.yaml file.
- Modify the access: grpc: section to set a new, higher limit for maxInboundMessageSize.
- The provided example sets the limit to 9,000,000 bytes (approximately 8.58 MiB), which is well above the message size that caused the error (6,200,677 bytes).
access:
grpc:
maxInboundMessageSize: 9000000
- Save the system.yaml file.
- Restart the application service for the new configuration to take effect.