We are currently facing a similar problem where the client stops receiving messages from the server. What we have observed is the application will perform as expected, receiving messages opening up the channel on the initial few visits, however after a period of time the channel on the client will not receive any more messages despite being established.
Diagnosis has been performed on both local dev mode and production instances and behaviour is the same, except on production it takes a longer period of time ( approximately 1 hr ) before reaching this channel state of not receiving on the client. The problem has been observed in both the latest versions of Chrome and Firefox. Through use of lsof and netstat it was found that a large number of sockets were being held open by the browser in a CLOSE_WAIT state, which once the process (firefox) that was holding these sockets was closed and released the channel started to receive again, although at a very slow rate ( the slow rate on recovery could be caused by the current task queue latency ). The problem does not exist if setting up a new channel with a new token every time, but when refreshing (disconnect/reconnect) the channel using the same token results in this problem where client stops receiving after a period of time. Still trying to find a solution to this problem. On Monday, 31 December 2012 07:00:42 UTC+11, [email protected] wrote: > > I've recently faced the problem. I've implemented some collaborative work > on my app. I've used the Channel API and it works really fine on localhost. > After deploy, the "update" in the other client is never received. why? > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
