As I understand it, the current push server is not "production" yet. As such, nothing has been adjusted on AWS to prevent its resource saving measures, including closing inactive connections after about a minute.
On Sep 12, 2013, at 6:10, Guillermo López Leal <[email protected]> wrote: > El 12/09/13 12:16, Vidor Gencel escribió: >> If we are sending a push notification every 15 seconds everything works >> fine, but when we pause sending for 2-3 minutes than it stops working. >> _______________________________________________ >> dev-b2g mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-b2g > > So you should check if you have the WebSocket to the push server alive. > This can be done: > > a) Using tcpdump in your device, and check if you have a closing > connection (which should reconnect to the server… so it might be > possible that you are not getting a "FIN" on your side). > > (also, please check if the same happens on 3G or in other wifi networks, > maybe your wifi has something strange. For example, we have a wifi with > proxy that is messing with the push and we do not have any > notifications, like your problem) > > b) Check the PushService.jsm debug logs. > > I would go with checking other networks (3G or wifi), and if the same > happens, we can go with the tcpdump or debug logs. > > Cheers, > > -- > Guillermo López [willyaranda] > http://mozilla-hispano.org > http://twitter.com/mozilla_hispano > http://facebook.com/mozillahispano > Certified Mozillian: https://mozillians.org/willyaranda > > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
