RFEM 6 API II C# | RpcException: "Received message exceeds the maximum configured message size."

API & Interfaces
,
1

Hi everybody,

I ran into this Exception just now:
Grpc.Core.RpcException : Status(StatusCode="ResourceExhausted", Detail="Received message exceeds the maximum configured message size.")

It happened after calling ApplicationRfem.get_results(resultsType: ResultsType.StaticAnalysisMembersInternalForces, filters: filters) on a small model, filterung for a single LoadCombination.

:magnifying_glass_tilted_left: My Question:

Is there any way to configure the gRPC message size with the C# Client?

Any help would be greatly appreciated.

3

Hey Nils!

Thanks for bringing up the issue with the ResourceExhausted exception. We wanted to let you know that in the next release of the C# client (hopefully today), we’re going to try increasing the message size limits to help solve this.

The plan is to raise the send and receive size limits in the gRPC settings, so you should be able to handle larger datasets without hitting the message size restriction.

We’re hopeful this will fix the issue you’ve been experiencing. Once it’s out, feel free to let us know how it works for you – we’d really appreciate the feedback!

Regards

4

Hi Tomas,

thank you so much for the quick reply! I appreciate it.
I will be patiently waiting for the new release then and give you a feedback once I tested it again.

But for my understanding: There are currently no plans to give the configuration of the message size to the user? Our use case involves reading large amounts of result data, and altough i didn't test it yet, i fear that even with an increased message size limit it could still be a problem.

Again, thanks so much for your time!

Best regards

5

Hi Nils,

The new release of the C# package 2.11.8 is now published, so feel free to test it. Currently, we have hardcoded the message size (both in and out) to 1 GB, as we cannot set it to "unlimited" like we do for the Python client.

There are no plans yet to allow users to configure this message size directly, but we are open to optimizing the client based on your feedback. Let's stay in contact and fine-tune it together as needed.

Best regards

6

Good news!

I tested it with a few examples, also considering some extreme cases and it works flawlessly now. The performance is impressive :slight_smile:

Should there be the need to increase the message size again, i will be in touch, but for now everything is fine.

Thank you for your time! Happy to resolve this issue so quickly.

1 Like