[GH-ISSUE #3] Unreliable Task Check pings to web server URL (using LG Optimus One P500) #1

New issue

Closed

opened 2026-02-28 01:22:41 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 01:22:41 +03:00

Owner

Originally created by @ghost on GitHub (Jun 26, 2011).
Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/3

We are noticing that the Task Check pings are getting delayed and don't necessarily come to the web server URL regularly. Following is a log of the webserver:

106.76.100.179 - - [26/Jun/2011:17:20:44 +0530] "GET /smsg/?task=send HTTP/1.1" 200 316 "-" "SMSSync-Android/1.0)"
106.76.100.179 - - [26/Jun/2011:17:21:54 +0530] "POST /smsg/ HTTP/1.1" 200 304 "-" "Apache-HttpClient/UNAVAILABLE (java 1.4)"
106.76.100.179 - - [26/Jun/2011:17:22:20 +0530] "POST /smsg/ HTTP/1.1" 200 304 "-" "Apache-HttpClient/UNAVAILABLE (java 1.4)"
106.76.100.179 - - [26/Jun/2011:17:36:07 +0530] "GET /smsg/?task=send HTTP/1.1" 200 559 "-" "SMSSync-Android/1.0)"
106.76.100.179 - - [26/Jun/2011:17:36:08 +0530] "GET /smsg/?task=send HTTP/1.1" 200 316 "-" "SMSSync-Android/1.0)"
106.76.100.179 - - [26/Jun/2011:17:36:09 +0530] "GET /smsg/?task=send HTTP/1.1" 200 316 "-" "SMSSync-Android/1.0)"

The POST pings are when we are sending test messages to the number that get correctly forwarded to the server. You may notice that the last three task check pings arrived within a second of each other and that they were not received on server for about 15 mins before that period. (We are using the time-period as 5 mins)

Originally created by @ghost on GitHub (Jun 26, 2011). Original GitHub issue: https://github.com/ushahidi/SMSSync/issues/3 We are noticing that the Task Check pings are getting delayed and don't necessarily come to the web server URL regularly. Following is a log of the webserver: 106.76.100.179 - - [26/Jun/2011:17:20:44 +0530] "GET /smsg/?task=send HTTP/1.1" 200 316 "-" "SMSSync-Android/1.0)" 106.76.100.179 - - [26/Jun/2011:17:21:54 +0530] "POST /smsg/ HTTP/1.1" 200 304 "-" "Apache-HttpClient/UNAVAILABLE (java 1.4)" 106.76.100.179 - - [26/Jun/2011:17:22:20 +0530] "POST /smsg/ HTTP/1.1" 200 304 "-" "Apache-HttpClient/UNAVAILABLE (java 1.4)" 106.76.100.179 - - [26/Jun/2011:17:36:07 +0530] "GET /smsg/?task=send HTTP/1.1" 200 559 "-" "SMSSync-Android/1.0)" 106.76.100.179 - - [26/Jun/2011:17:36:08 +0530] "GET /smsg/?task=send HTTP/1.1" 200 316 "-" "SMSSync-Android/1.0)" 106.76.100.179 - - [26/Jun/2011:17:36:09 +0530] "GET /smsg/?task=send HTTP/1.1" 200 316 "-" "SMSSync-Android/1.0)" The POST pings are when we are sending test messages to the number that get correctly forwarded to the server. You may notice that the last three task check pings arrived within a second of each other and that they were not received on server for about 15 mins before that period. (We are using the time-period as 5 mins)

kerem closed this issue

2026-02-28 01:22:41 +03:00

kerem commented

2026-02-28 01:22:42 +03:00

Author

Owner

@ghost commented on GitHub (Jun 26, 2011):

Just noticed one specific behavior - when the phone screen was on, the task pings were being sent at the specified interval. And when the phone screen went off, the task check pings were not sent.

Also learnt from the url:
http://stackoverflow.com/questions/5345344/app-seems-to-stop-working-when-the-screen-goes-to-sleep

that this may be an expected behavior on Android.

We are looking to run this phone with a 3G connection in an unattended mode. Should SMSSync, then, keep the phone in active state so that it can work as expected??

@ghost commented on GitHub (Jun 26, 2011): Just noticed one specific behavior - when the phone screen was on, the task pings were being sent at the specified interval. And when the phone screen went off, the task check pings were not sent. Also learnt from the url: http://stackoverflow.com/questions/5345344/app-seems-to-stop-working-when-the-screen-goes-to-sleep that this may be an expected behavior on Android. We are looking to run this phone with a 3G connection in an unattended mode. Should SMSSync, then, keep the phone in active state so that it can work as expected??

kerem commented

2026-02-28 01:22:42 +03:00

Author

Owner

@eyedol commented on GitHub (Jun 30, 2011):

Thanks for reporting this tangereinfotech. It's a known issue which should be fixed in the next release.

@eyedol commented on GitHub (Jun 30, 2011): Thanks for reporting this tangereinfotech. It's a known issue which should be fixed in the next release.

kerem commented

2026-02-28 01:22:42 +03:00

Author

Owner

@mandric commented on GitHub (Dec 14, 2012):

@eyedol we are experiencing this issue on latest SMSSync only with the task checking functions. running android 2.3.6 on a samsung pocket galaxy S5300. just wondering if this is a known issue with task checking... thanks!

@mandric commented on GitHub (Dec 14, 2012): @eyedol we are experiencing this issue on latest SMSSync only with the task checking functions. running android 2.3.6 on a samsung pocket galaxy S5300. just wondering if this is a known issue with task checking... thanks!

kerem referenced this issue

2026-02-28 01:24:16 +03:00

[PR #1] [MERGED] Sending of multipart messages #348