Unable to configure maxInboundMessageSize with gatling-grpc-java 3.13.5

General discussions
1

Hello,
I am using Gatling 3.13.5 with Maven and the gatling-grpc-java module.

We are performing a gRPC call that retrieves an attachment (~7–10 MB).
When running the test with Gatling, we receive:

RESOURCE_EXHAUSTED: gRPC message exceeds maximum size 4194304

However, the same call works correctly with tools like Kreya, so the server seems to be functioning properly.

The gRPC protocol is created as follows:

GrpcProtocolBuilder protocol = grpc.forAddress(configProperties.getGrpcHost(), configProperties.getGrpcPort())
        .useInsecureTrustManager();
return scn.injectOpen(CustomInjectionStrategy.createOpenInjectionStep(scenario)).protocols(protocol);

From the error, it appears that the default client maxInboundMessageSize (4MB) is being enforced.

However, I cannot find any way in the Java DSL to configure maxInboundMessageSize (e.g. via channel builder customization).

Is there currently a supported way to configure maxInboundMessageSize when using the Java DSL?

Thank you in advance.

2

Hi,

Could you please first upgrade to Gatling 3.14.9 and see if you still experience an issue?

1 Like
3

I upgraded to 3.14.9 and behavior is the same.

found RESOURCE_EXHAUSTED

4

hi Stephane,

do you have something else to suggest me?

5

Hi

I think we’ll release gatling-grpc 3.14.9.2 next Tuesday.

1 Like
6

Please inform me whenever 3.14.9.2 is released from your side. :slight_smile:

Many thanks.

7

Hello,

Yes, it’s out :tada:

8

Hi Stephane,

I just tried by upgrading grpc-java to 3.14.9.2 and it worked (after resolving small conflicts) without any code change on my side.

Many thanks,

Michalis

1 Like