Channel API not working properly

[Philip]

I have had an app working with channels deployed to App Engine for a
while now. I have made some changes to the code and haven't isolated a
simple channels test yet, but channels appear to not be working on my
Mac using Chrome or Safari due to issues at Google. At first it
appeared to be a Safari only issue. Now, channels are not working with
either browser due to a client side (javascript) error.

Uncaught CustomError: Service for "ea" is not registered

This error is coming for google downloaded code that starts with:

369.talkgadget.google.com/talkgadget/d?

I have checked the Apps Status Dashboard (http://www.google.com/
appsstatus#hl=en) and there are no reported issues with Google Talk.

Any ideas?

[ramesh]

I am facing the same issue from today morning onwards.

I am getting error in following URL:

https://139.talkgadget.google.com/talkgadget/d?token=AHRlWrq-vS9cLNrNyVvqXp9QCrMOifivML_dS57svS7TAnJPXDarIUdQeeVLpwneZ6WkZhM-MISnN4odUesmAEgqqMIfxa0Y0srUBslOf92L2Qiw5GiXc1iSAUzSIDfSs6LuyGVieQjC90TQgkT2JuMwYlErkzWKS3tvJY57_pfDCY3CCZEvM_4&xpc={%22cn%22%3A%226KbHSMiBJM%22%2C%22tp%22%3Anull%2C%22ppu%22%3A%22http%3A%2F%2Fwww.google.com%2Fxpc_blank%22%2C%22lpu%22%3A%22http%3A%2F%2F139.talkgadget.google.com%2Ftalkgadget%2Fxpc_blank%22}

Any help?

[Bay]

Same problem... Channel API not working. Similar error as Philip

[Andrin von Rechenberg]

We are facing the same problem,

Has anyone filed a production ticket?

-Andrin, from MiuMeet

On Thu, Sep 15, 2011 at 11:12 AM, Bay <troe...@gmail.com> wrote:

Same problem... Channel API not working. Similar error as Philip

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.

To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/8QTBSzn3vz0J.

To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Strom]

Same here and it's not limited to chrome, doesn't work in IE9 either.

[Andrin von Rechenberg]

I have filed a produciton issue ticket.

Please star it so google gets aware about it:

http://code.google.com/p/googleappengine/issues/detail?id=5903

The problem also appears on all mobile phones.

This is clearly a bug on googles side.

-Andrin

[Tom Newton]

Same here... Has been working flawlessly for a few months now.

Uncaught CustomError: Service for "ea" is not registered is what I'm
seeing this morning.

Have starred your ticket.

T

[GK]

Same here.

I have starred the issue.

[Strom]

So 6 hours of the Channel API being down and no word from Google. I
wonder, would this fall under the SLA in the future?

[Takashi Matsuo (Google)]

App Engine team is aware of this issue, and working on the fix. We'll update in the downtime notify group.

-- Takashi Matsuo

[ramesh]

Any ETA from Google to fix this issue. We are waiting on this one.

[Moishe]

ETA is about 2 hours for complete rollout of fix.

[Bay]

Why dont you do what other services do: Write small apps that continously make sure that all the functions are working in production. Datastore puts, datastore reads, channel broadcasting, etc... Then you would have really quickly noticed that an issue was preventing the push-function from working.

This is probably the third production issue my app have been affected by - and it always takes 6+ hours to fix. You really, really need to look into quality assurance.

No. Really. Its okay that you guys decided to make the whole GAE-platform highly profitable. You're a company. Its expected. But with downtime like this on functions that you are going to charge for - that's simply not going to be acceptable.

[Strom]

It seems fixed now, or at least my app's channel feature started
working.

I agree with Bay, that there should be more test coverage / status
reporting. I've been defending GAE even with the recent price increase
drama, but it's getting hard with a 9 hour outage addition. My main
defense of the price increase is that I don't have to worry about
servers breaking down and I can sleep easily. However it turns out
that stuff doesn't get fixed in a reasonable amount of time and what's
worse, there's a minimal amount of communication from Google on what
the hell is actually going on.

[FastGeert]

Yes, https://rogerth.at is also suffering from this exact problem.

Please fix it asap, my customers are affected by this.

[SYUJI]

Same problem is occured.
via Chrome and Firefox
from japan

[Brian Immel]

Same here... Started within the last day for me.

[ShinTEZUKA]

Me too... I got that error a few hours ago. But 7 hours ago, it woks
fine(in JAPAN).
And it doesn't work on Android too.

[James Broberg]

OpenID service has also been down for us for about 6 hours or more.

[balaa]

I'm experiencing issues with the Channel API only being able to
successfully send 1 message to my connected clients. After the one
message is received any subsequent messages are not received by the
client until I reestablish the socket connection?

Is this related to this service outage?

Client is google chrome

[gae channel user]

http://www.help-live-chat.com is suffering too and the same error
still persists after many errors. Keeping an eye out on the outage
page but no activity there.