Re: [grpc-io] [grpc-java 0.14.0] gRPC calls not working after a certain period.

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,

Re: [grpc-io] [grpc-java 0.14.0] gRPC calls not working after a certain period.

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

Re: [grpc-io] [grpc-java 0.14.0] gRPC calls not working after a certain period.

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

Re: [grpc-io] [grpc-java 0.14.0] gRPC calls not working after a certain period.

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

Re: [grpc-io] [grpc-java 0.14.0] gRPC calls not working after a certain period.

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