Yeah. Issue has been fixed it seems. Brought back the old production version of our app to default which had real time notifications enabled. Working fine as expected. Thank you very much :)
On Saturday, January 7, 2017 at 8:01:38 AM UTC+5:30, Ster Nem wrote: > > And of course after wasting all this time, it looks like it now works on > our sandbox environment. > > Of course my product environment is down because my quota has been > exceeded. 7 hours til reset. I hope Google compensates me for at least > today's "overuse" and more since my team has lost their Friday evening.. > > On Friday, January 6, 2017 at 9:26:34 PM UTC-5, Ster Nem wrote: >> >> Further details as my team have been debugging this for the past 3.5 >> hours. >> >> This part on our server returns error free: >> ChannelService channelService = >> ChannelServiceFactory.getChannelService(); >> token = channelService.createChannel(clientId, 1439); >> >> >> When we try and use this token it fails and as Ananthakrishnan desribes, >> our GWT code is setup to retry by creating a new channel. This killed our >> quota. >> >> We also have a java client using this channel and we are able debug. We >> are noticing that our parsing logic for the response from >> talkgadget.google.com doesn't seem to give us valid results. Something >> is wrong on that end. >> >> On Friday, January 6, 2017 at 8:53:10 PM UTC-5, Ananthakrishnan >> Venkatasubramanian wrote: >>> >>> Core problem for this issue is socket onopen handler is not getting >>> invoked instead onerror is getting called again and again. We are creating >>> a new channel token in onerror handler. So again and again, channel token >>> will be created, onerror handler invoked and it never goes to onopen >>> handler. The problem started on 07-JAN-2017 SATURDAY around 3:20 or 3:30 AM >>> IST onwards and it is still continuing. So far for these many years/days it >>> was working fine. Waiting for the fix so that we can turn on the real time >>> notifications back in our system. >>> >>> On Saturday, January 7, 2017 at 7:03:20 AM UTC+5:30, Ananthakrishnan >>> Venkatasubramanian wrote: >>>> >>>> Yeah. Facing the same issue and the application got >>>> crashed/continuously reloaded for the users. Please address this a.s.a.p. >>>> Currently we have disabled the real time notifications and addressed the >>>> production app issue. >>>> >>>> On Saturday, January 7, 2017 at 4:57:25 AM UTC+5:30, Ster Nem wrote: >>>>> >>>>> I use app engine channels to ensure my clients receive real-time >>>>> orders at their restaurant that they can fulfill. >>>>> >>>>> Within the past hour or so, I'm now getting this message when the >>>>> client side software tries to establish a channel: >>>>> >>>>> com.google.apphosting.api.ApiProxy$OverQuotaException: The API call >>>>> xmpp.CreateChannel() required more quota than is available. >>>>> >>>>> I'm definitely not over the quota, and I even have an idle sandbox app >>>>> engine id and can't seem to establish channels testing there. >>>>> >>>>> Anyone else see this issue? Can someone look into it? >>>>> >>>> -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/fbacdd22-23be-48ec-8ad3-4a22ebbdad09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
