GCM messages getting delayed even after time_to_live=0

206 views
Skip to first unread message

Abhishek Kumar Gupta

unread,
Mar 27, 2014, 1:39:04 PM3/27/14
to andro...@googlegroups.com

We send daily push notifications(around 80000 to 100000 in number) using GCM. The users complained that the notifications arrive late, about 12 hours late. So, we changed time_to_live to 0 and delay_while_idle as false. Even after two weeks of changing these values, the notifications are reaching very late.

Also the GCM message status in developer console shows more than 50% of messages in stored state.

Any help or guidance to resolve the issue will be well appreciated

Costin Manolache

unread,
Mar 28, 2014, 1:54:49 PM3/28/14
to andro...@googlegroups.com
Are you seeing messages with TTL=0 that are delivered > 5 min late ? Please send me sample message id / registration id for this case.
TTL=0 should be dropped if the device is not found connected, it would be a bug if it is not. 

50% stored is not unusual - it means the device was not connected when the message was sent. With a lot of tablets on wifi,
and phones without network - it is not unexpected.

Costin


--
You received this message because you are subscribed to the Google Groups "android-gcm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-gcm...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-gcm/f344b539-05a5-4f60-a27e-057acdf5c35d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Message has been deleted

Abhishek Kumar Gupta

unread,
Mar 31, 2014, 5:06:57 AM3/31/14
to andro...@googlegroups.com
Hi Costin Manolache, thanks for the reply. Please find the some of the messages those taken >5min:

Message 1:
Send Time : 2014-03-31 12:06:02 
Data:{"delay_while_idle":false,"time_to_live":0,"registration_ids":["APA91bGDP1RRS-7m-DeiMJonFoPUvLWk--9gRnySa4SeBBfrO-_Up2C28rMc3CzG7R9TG5mV5DdtWk7QU_k7azCg9B4-Lpi-Xszv3LWS732J4hE3FOB77x2dcllbvytF-bolm13tekQs_cseke2HhZq1CxVZcZz2Eg"],"data":{"message":{}
Response from GCM:{"multicast_id":8435043718794004247,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"0:1396247762729317%88ce056ef9fd7ecd"}]}
Received At: 2014-03-31 12:24:06


Message 2:
Send Time : 2014-03-31 12:02:05
Data:{"delay_while_idle":false,"time_to_live":0,"registration_ids":["APA91bEPr-FK1g0LAJsJADDhYr6aMOROfnFPVfa7EfPNtkcNapWgEkD6IUTRYZ5YvQOLQfyMFPd1hjEJRvfNY_khIFx1nWlHqY9ik7O-tTEsG-Q9sQ6vEdacvCqCkxrJyj54R83rhNzQnTnzf4UNLBpaellHXV16UA"],"data":{"message":{}
Response from GCM:{"multicast_id":6797307906689570261,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"0:1396247525322905%88ce056ef9fd7ecd"}]}
Received At: 2014-03-31 12:24:52


Message 3:
Send Time: 2014-03-31 11:36:02
Data:{"delay_while_idle":false,"time_to_live":0,"registration_ids":["APA91bH-1eBebliwvcLx6fven0qAELXDJsRPjVA8YdlDXkn_G0GXmRzP3gVute43YRNtXtwGPhzc9YjU-dzqAERIEcdUty6PY6eovVMjxiQ9EBPdmNnn5Of7ZSQChyCf__t-gBQjFRO6Odgj4KaDOYFdT9bvXHUsCw"],"data":{"message":{}
Response from GCM:{"multicast_id":4957950410713029653,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"0:1396245962479601%88ce056ef9fd7ecd"}]}
Received At: 2014-03-31 12:26:18


Message 4:
Send Time: 2014-03-31 11:48:08
Data:{"delay_while_idle":false,"time_to_live":0,"registration_ids":["APA91bFmG89JB0Tqeefu5HSDBfOw4IJcu2od0Qi7cfuxWaRtWRiFC1lK9m3o8nHTZL9bgLQ72xthHd3u2AJ3Hqel0psQNMJ7yg_7Xj2p5_HU-3HgdkHpYZu91wW5y4aQfnlPozRqiUMseaMrCOSuvZZHI4Dj3j0-CAMiRCvyzckL_-FGs7IJ8Y4"],"data":{"message":{}
Response from GCM:{"multicast_id":6096679578549763749,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"0:1396246688602402%88ce056ef9fd7ecd"}]}
Received At: 2014-03-31 12:26:45



Message 5:
Send Time:2014-03-31 10:56:04
Data:{"delay_while_idle":false,"time_to_live":0,"registration_ids":["APA91bGlxbCm6emJO9Ls-91JmYhfN94K_EiQFvN1PiPodmJRJokOiVMpIxDEejMiIDp6Pvnu65YH7c4t8L1j10fNvJxUodP3Ffwp01Gd6Ctf7eEk2mJOVgTutX4XxVBkpKnXSqxmcB0a3wXWyvb7dzgd8u6YY7wUFw"],"data":{"message":{}
Response from GCM:{"multicast_id":6992492474471459467,"success":1,"failure":0,"canonical_ids":0,"results":[{"message_id":"0:1396243564146290%88ce056ef9fd7ecd"}]}
Received At: 2014-03-31 12:26:56

montyb...@gmail.com

unread,
Jun 23, 2014, 9:04:37 AM6/23/14
to andro...@googlegroups.com, akgae...@gmail.com
Hi,

 We have a similar problem with our application, notifications arrive late, after hours. Could you find a solution or the reason of this problem. I appreciate if you share your last results.

Thanks.

Rupert Rawnsley

unread,
Mar 2, 2015, 6:57:25 AM3/2/15
to andro...@googlegroups.com, akgae...@gmail.com
me too

I've set time_to_live to zero or to a very small number of seconds and the message is still delivered once the device is tuned on again hours later. It's frustrating because this was a neat mechanism for sending "best effort" messages to devices that happen to be active.

Tingmui Li

unread,
Mar 3, 2015, 4:52:14 AM3/3/15
to andro...@googlegroups.com, akgae...@gmail.com
Please send us the message ID or registration ID that is experiencing this problem.

Rupert Rawnsley

unread,
Mar 3, 2015, 5:21:11 AM3/3/15
to andro...@googlegroups.com
Thanks for the quick response. In trying to reproduce the problem for you, I've discovered a bug on our side: basically we were not actually setting the time_to_live field properly, but we couldn't see that in the raw message JSON because we are using the old Java library to access the server.

Please chalk it up to "user error" and accept my apologies!
Reply all
Reply to author
Forward
0 new messages