> On Apr 2, 2015, at 8:14 AM, Eric Levine <[email protected]> wrote: > > We are using the .Net version of CBL, and it stops receiving changes from the > Sync Gateway if there is 5 minutes or more of inactivity. When I look at the > Sync Gateway logs, I see that the Pull Replicator sets the heartbeat query > parameter to 5 minutes when it requests the changes feed. The status of the > pull replicator doesn't change from idle, and it doesn't fire a changed event > at that time.
Well, it wouldn’t fire any event if there’s inactivity. Are you talking about a situation where, after >5 minutes of inactivity, the gateway does have a change but the client doesn’t receive it? Can you describe the sequence of events (and what gets logged on either side) in more detail? Also, please describe the network topology between SG and CBL — in particular any proxies/gateways/load-balancers (especially ones from cloud services like AWS, which are known for terminating ‘idle’ sockets.) —Jens -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/E983CF7B-0F48-46BC-8DE7-8BF802A10EA8%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
