Hi team,

I just double checked and looked overall again in our application, the root
cause is related to my missing look at the config file.
I have not setted timeout on the RestAPI side, that is the reason why when
receiving the large stream message it was a deadline exception.

Thanks to your team.

Tony.

On Tue, Aug 26, 2025 at 6:30 PM Kannan Jayaprakasam <[email protected]>
wrote:

> Is the RPC not waiting for the 2 minutes that you set? Are you using some
> gRPC to REST transcoder and are trying the setting on this gateway?
>
> On Tue, Aug 26, 2025 at 9:20 AM Tony B <[email protected]> wrote:
>
>> Hi team,
>>
>> When I am working with stream in gRPC, I am able to test successfully to
>> get stream message. However, when integrating to receive response from gRPC
>> to RestAPI, I have an error is related to deadline exception due to the
>> stream message is large.
>>
>> I already tried to adjust multiple ways like set context with timeout up
>> to 2 minute. However, it does not work with large message.
>>
>> Do does team have any suggestion for me to handle about that issue.
>>
>> Thanks in advances !
>>
>> Tony
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "grpc.io" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To view this discussion visit
>> https://groups.google.com/d/msgid/grpc-io/ea950348-d9db-42eb-adfb-2c2d20d2513en%40googlegroups.com
>> <https://groups.google.com/d/msgid/grpc-io/ea950348-d9db-42eb-adfb-2c2d20d2513en%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/grpc-io/CAE3waXLgObi3k_41r_7kUAJ1C8dd-Qk7_6N4Hz5W%2BQpZ7obZRw%40mail.gmail.com.

Reply via email to