I'm using grpc java on Android and I found a very weird issue. After a
certain period a ManagedChannel no longer works.
When this issue happens, grpc calls stopped working so I had to close and
restart my app.
I instantiated a ManagedChannel when there is no cached channel then cache
it until t
On Sat, Jun 25, 2016 at 4:36 AM, Taehyun Park
wrote:
> I'm using grpc java on Android and I found a very weird issue. After a
> certain period a ManagedChannel no longer works.
>
Was that after a period of inactivity? Were you on good WiFi (one that you
trust), bad WiFi, or cellular?
I instanti
I've confirmed that a period of inactivity is about 60 minutes. I added an
idle timer which release a channel after a period of inactivity but a newly
created channel is still unusable.
Below is the logcat once the channel is terminated and created.
06-26 13:41:47.612 28807-28891/com.test I/Manag
Sorry for confusions. The logcat was not the same device and the timer I
added didn't work properly. Releasing resources by shutting down a channel
when there is a period of inactivity solved my issue.
On Sunday, June 26, 2016 at 1:06:06 AM UTC+9, Eric Anderson wrote:
>
> On Sat, Jun 25, 2016 at
Whew. I saw your email this morning but didn't have time to reply saying I
had so clue what could cause that. Glad it's working for you, and you can
look forward to built-in idleness.
And an hour makes sense for the tcp connection to (silently) break with a
home network, since there is a NAT invol
FYI: 3.0.0-pre1 includes support for auto-idling Channels (and keepalive
for OkHttp). So you may be able to simplify your code now.
On Sun, Jun 26, 2016 at 1:01 PM, Eric Anderson wrote:
> Whew. I saw your email this morning but didn't have time to reply saying I
> had so clue what could cause th
Thank you for this update. I updated to 1.0.0-pre2 and got rid of my own
timer that releases a created channel after a certain period.
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
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.
On Saturday, July 30, 2016 at 2:22:29 AM UTC+9,
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. Wh
Hi Eric,
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 coul
On Sat, Sep 17, 2016 at 12:40 AM, wrote:
> 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?
>
The channel itself is lazy, so you could just cr
11 matches
Mail list logo
