I'm trying to take a look at this now. One thing I noticed is that your app is using https. I know of one bug with https, and a fix will roll out for that in a couple of weeks. Does this problem still happen if you use http?
Also to make debugging easier, you can directly include http://talkgadget.google.com/talkgadget/channel.js instead of /_ah/ channel/jsapi. If you get a chance to make that change let me know and I can take another look. Sorry for the trouble! On Dec 12, 8:23 am, Flori <[email protected]> wrote: > Okay, i think the first issue, the high CPU avg, is normal.. but the > second problem still exists! Every time i call channel.open(); the > following stack trace appears: > > Uncaught Error > h jsapi:1 > E djsapi:80 > $ jsapi:75 > Gd.open jsapi:81 > loadApplication application.js:165 > Ext.Ajax.request.success application.js:33 > Ext.data.Connection.Ext.extend.onComplete sencha-touch.js:6 > Ext.data.Connection.Ext.extend.onStateChange sencha-touch.js:6 > (anonymous function) sencha-touch.js:6 > > So can it may be that the problem is caused with the mix of Sencha > Touch and the Channel library? I can't see what $ or E or h stands > for. > > cheers -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. 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-java?hl=en.
