Stream stops receiving messages after 4 received about ngx-grpc HOT 4 CLOSED

@smnbbrv thanks for the reply. Ended up debugging through ngcc and found it was an assertion error due to have a too big of integer defined at int32 in the proto file. Changed to int64 and all good now.

I am indeed using the improbable websocket transport, how would this affect me with longer requests? This is the first time I've used this client so please pardon the basic questions.

Thanks again for replying.

from ngx-grpc.

Hi,

sounds like some sort of a timeout.

There are several places you can check: your load balancer, your envoy and finally your server implementation.

The server streaming (unless you use websocket transport from improbable) is implemented as a never ending request (the stream is delivered in chunks until done), so it is affected by any kind of timeout settings on any proxy in between.

from ngx-grpc.

The websocket should not suffer from this I assume. That's a standard implementation issue only. TBH I haven't tried the websocket transport yet, good to know it works 😂

from ngx-grpc.

@smnbbrv Thanks again.

from ngx-grpc.