I've also observed the same issue where after a while, my GPRC calls from
Android start failing.
I lazily create my stub, so I've tried checking if stub is disconnected,
and creating a new one in that case, but I'm still not winning. Is there
some solution that you or anyone else could suggest?
On Saturday, 17 September 2016 07:22:58 UTC+2, Eric Anderson wrote:
> Catching up on old threads...
> It sends a GO_AWAY packet when the status is changed to IDLE. Do I have to
>> release this channel or is it safe to reuse this channel? If I can reuse
>> the channel, it looks like I no longer need to release the channel.
> The channel should have been safe to reuse. When the channel is IDLE, it
> should be in a very similar state to a newly-created channel.
> On Thu, Aug 11, 2016 at 11:51 PM, Taehyun Park <gold.d...@gmail.com
>> I had to restore my own timer which releases a channel because auto-idle
>> still caused the same problem. The grpc calls still didn't go through after
>> a certain period so I guess releasing a channel is the only way if I don't
>> want to use keepalive.
> That's unfortunate. What delay did you use for auto-idle? It sounds like
> you didn't enable OkHttp's keepalive, but that should really only help if
> the RPCs take a long time before the response arrives.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.