I don't know if it's the same issue but my application is also encountering
bugs with the channel API
When I call: channel.open() the message below is displayed in my browser:
"Failed to load resource: server responded with a status of 400 (Unknown
SID)"
As a consequence, my users can't see the other connected users. That's
really damaging their experience.
Thanks for looking at this problem
Dam
Le jeudi 26 juillet 2012 14:20:13 UTC+2, Aleksei Rovenski a écrit :
>
> Hi all,
>
> We have an emergency in our app (yagoloo-chat). We are using Channel API
> and about 2 hours ago smt very bad has happened.
> Where it usually took 20-40 millis to send a message through the channel
> (not delivery time, I mean api method lock time), now it takes 4-5 seconds.
> Yes SECONDS, so when we
> call ChannelServiceFactory.getChannelService().sendMessage(""), it blocks
> for 4-5 seconds. We are using queues to send messages, where each task
> sends 5 at max (can be less) and at the moment it shows 17 seconds average
> execution time. We also have appstats enabled which clearly show
> sendMessage() eating the time.
> Needless to say our instances have skyrocketed, where usually we had 2-3,
> now there are 16. We are not paying for premium support, does it mean we
> will have to pay for that??!
> Please someone at google take a look at this. I have filed production
> issue...
>
> cheers,
> Aleksei
>
>
Le jeudi 26 juillet 2012 14:20:13 UTC+2, Aleksei Rovenski a écrit :
>
> Hi all,
>
> We have an emergency in our app (yagoloo-chat). We are using Channel API
> and about 2 hours ago smt very bad has happened.
> Where it usually took 20-40 millis to send a message through the channel
> (not delivery time, I mean api method lock time), now it takes 4-5 seconds.
> Yes SECONDS, so when we
> call ChannelServiceFactory.getChannelService().sendMessage(""), it blocks
> for 4-5 seconds. We are using queues to send messages, where each task
> sends 5 at max (can be less) and at the moment it shows 17 seconds average
> execution time. We also have appstats enabled which clearly show
> sendMessage() eating the time.
> Needless to say our instances have skyrocketed, where usually we had 2-3,
> now there are 16. We are not paying for premium support, does it mean we
> will have to pay for that??!
> Please someone at google take a look at this. I have filed production
> issue...
>
> cheers,
> Aleksei
>
>
Le jeudi 26 juillet 2012 14:20:13 UTC+2, Aleksei Rovenski a écrit :
>
> Hi all,
>
> We have an emergency in our app (yagoloo-chat). We are using Channel API
> and about 2 hours ago smt very bad has happened.
> Where it usually took 20-40 millis to send a message through the channel
> (not delivery time, I mean api method lock time), now it takes 4-5 seconds.
> Yes SECONDS, so when we
> call ChannelServiceFactory.getChannelService().sendMessage(""), it blocks
> for 4-5 seconds. We are using queues to send messages, where each task
> sends 5 at max (can be less) and at the moment it shows 17 seconds average
> execution time. We also have appstats enabled which clearly show
> sendMessage() eating the time.
> Needless to say our instances have skyrocketed, where usually we had 2-3,
> now there are 16. We are not paying for premium support, does it mean we
> will have to pay for that??!
> Please someone at google take a look at this. I have filed production
> issue...
>
> cheers,
> Aleksei
>
>
--
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/-/y3Jg-PY7XoUJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en.
