Thanks for the responses.  I basically figured most of that state table 
just by playing some with it :)  
The true vs false on getState was still a  mystery.  As you indicate it 
never did anything for me.  I think if it was working it would be 
beneficial.  What I'm trying to achieve was prioritize which endpoints are 
most likely to succeed to try them first.  Nothing I did took an IDLE to 
RUNNING except an actual RPC but then that would be too late.   

On Tuesday, March 6, 2018 at 6:45:16 PM UTC-5, Eric Anderson wrote:
> On Mon, Mar 5, 2018 at 11:16 AM, < <javascript:>> wrote:
>> Thanks ..  So when I bring down the remote server Current state goes from 
>> READY to IDLE .  the channel stays in shutdown terminated both to false. 
>> It seems to stay that way.
> On Mon, Mar 5, 2018 at 11:28 AM, < <javascript:>> wrote:
>> I should have pointed out that when queried the state I was using 
>> .getState(true);
> To close the loop here, we've reproduced a bug that would impact this 
> conversation: . 
> getState(true) is currently broken and does not trigger a connect if the 
> channel was previously connected (there's a few cases it still will, but 
> they will be uncommon). It does work properly for a new channel, but not 
> for reconnecting.
> Note that we still properly reconnect when doing an RPC. It's only the 
> getState(true) API that is broken.

You received this message because you are subscribed to the Google Groups 
"" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
To view this discussion on the web visit
For more options, visit

Reply via email to