With gRPC active, you see error messages like the following in logs:

RESOURCE_EXHAUSTED: gRPC message exceeds maximum size

Cause:

Your content objets are larger than the default maximum gRPC message size of 4 MB.

Solution:

Add the following properties for client applications. These double the maximum message size to 8 MB. If you have even larger content objects, you might want to increase this value even more. The concrete message size in the error message will give you a hint on how much to increase the maximum message size. Keep the value in sync with the server configuration (see below).

spring.grpc.client.channels.cap.max-inbound-message-size="8388608B"
spring.grpc.client.channels.wf.max-inbound-message-size="8388608B"

Correspondingly, add the following property for servers. Keep the value in sync with the client configuration (see above).

spring.grpc.server.max-inbound-message-size="8388608B"

Applications do not respond on request. The CPU load of the applications is high, the thread dump shows threads that use nio classes.

Possible cause:

Problems with the CORBA ORB.

Possible Solution:

Add the following ORB property as a system property for the affected applications:

-Dcom.sun.corba.ee.transport.ORBUseNIOSelectToWait=false