Reduce "rapid-fire" messaging from GTalkSMS to XMPP server

[GoogleCodeExporter]

As an operator of a jabber server, I've noticed GTalkSMS users causing issues 
by having the application send "rapid-fire" messages to the XMPP server, 
sending many messages in a short period of time with repeat content, even the 
welcome message. Bursts of 15-30 identical messages are not uncommon.

I believe this may be related to the receiving JID being off-line (or not 
immediately confirming) at the time, but have not been able to verify (since I 
don't own a smartphone with the app). It should be noted that these messages 
are commonly stored on the xmpp server to be delivered the moment the target 
JID signs on, and that repeatedly sending the message serves no purpose for the 
receiving JID. If this is caused by requiring confirmation of receipt, then be 
aware that server-to-server connections may take some moments to be 
established, as well. Jabber/XMPP is designed for "instant" messaging, but not 
necessarily "real-time" messaging.

This is a serious issue and has me consider blocking any GTalkSMS users from my 
server because it causes unnecessary load. Please treat this defect with 
urgency. Thanks.

Original issue reported on code.google.com by mcwerew...@gmail.com on 18 Feb 2014 at 7:05

[GoogleCodeExporter]

Hello, thanks for your report. 
I'll need some informations about the messages that are sent several times:
- Do they target the exact same JID (or with different resources)?
- Is it exactly the same message?
- Does it happen with all the message or only one or few types of messages?
- Could it be the same message splitted in several small messages?
- Which server are you using? Can I have an account with some privileges to see 
logs and test potential fixes?

I assume that you cannot post or send me any logs because of privacy issues, 
but if you can provide me some answers it will help me a lot to solve this 
issue.

Original comment by Florent....@gmail.com on 18 Feb 2014 at 11:32

• Changed state: Accepted

[GoogleCodeExporter]

- They target the exact JID as far as I can tell. The users involved don't seem 
to be using many different resources to begin with, either. Certainly not in 
the double digits.
- It is exactly the same message, repeated.
- It happens with different messages (Welcome, x is calling, and even battery 
status messages)
- It's not one message split up, it is a repeat message. Large messages (e.g. 
the response to help) is delivered as a single message without problems, so 
it's not a message size limitation or similar.
- I'm using OpenFire (3.9). I'm sorry but I cannot give you an admin account on 
my production server; I suggest you make a test setup yourself (it's cross 
platform, and very easy to set up). Using the debug logging and packet auditing 
features should give you all the information needed.

Original comment by mcwerew...@gmail.com on 19 Feb 2014 at 12:13

[GoogleCodeExporter]

Example log entries, anonymized:

[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:27 PM]   {{gtalk app JID}}:  Battery level 70%
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:36 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[5:49 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:02 PM]   {{user JID}}:   batt
[6:02 PM]   {{gtalk app JID}}:  Battery level 64%
[6:07 PM]   {{gtalk app JID}}:  Battery level 60%
[6:08 PM]   {{user JID}}:   batt
[6:08 PM]   {{gtalk app JID}}:  Battery level 60%
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:21 PM]   {{gtalk app JID}}:  Welcome to GTalkSMS 4.4.1. Send "?" for getting 
help.
[6:23 PM]   {{user JID}}:   batt
[6:23 PM]   {{gtalk app JID}}:  Battery level 58%
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:41 PM]   {{gtalk app JID}}:  [[contact info scrubbed]] is calling…
[6:47 PM]   {{user JID}}:   batt
[6:47 PM]   {{gtalk app JID}}:  Battery level 52%
[6:47 PM]   {{user JID}}:   where
[6:47 PM]   {{gtalk app JID}}:  Start locating phone
[6:47 PM]   {{gtalk app JID}}:  Last known location
[6:47 PM]   {{gtalk app JID}}: 
    http://maps.google.com/maps?q={{nnnnnn}},{{nnnnnn}} accuracy: 1652.000000m  
altitude: 0.000000  speed: 0.000000m/s  provider: network
[6:47 PM]   {{gtalk app JID}}: 
    http://maps.google.com/maps?q={{nnnnnn}},{{nnnnnn}} accuracy: 33.000000m  
altitude: 0.000000  speed: 0.000000m/s  provider: network
[6:48 PM]   {{user JID}}:   where:stop
[6:48 PM]   {{gtalk app JID}}:  Stop locating phone
[6:50 PM]   {{gtalk app JID}}:  Battery level 50%

Original comment by mcwerew...@gmail.com on 19 Feb 2014 at 12:24

[GoogleCodeExporter]

I'm running some tests with openFire 3.8.2 without reproducing the issue yet.
I'm using Message Audit Policy too see messages, do you have another way to 
monitor messages?

By reading your logs it seems to be related to the application's notifications 
(calls, battery...).
Command seems ok (1 answer per command).
Do you have the version of GTalkSMS in your logs (to check if it's related to 
the new or an old version)?

Thanks

Original comment by Florent....@gmail.com on 22 Feb 2014 at 1:41

[GoogleCodeExporter]

The gtalksms version is listed in the log entries posted (4.4.1)

It seems there is a single response to a request if a user is online - I think 
the problem may occur if the receiving user (on the remote server e.g. gmail) 
is offline or there is no immediate confirmation of receipt of the notification 
message set. Of course in a practical situation this occurs very often.

You should be able to monitor the messages as well by installing the 
"monitoring" plugin (formerly Openfire Enterprise but made free a while back).

Original comment by mcwerew...@gmail.com on 22 Feb 2014 at 2:15

[GoogleCodeExporter]

I'll install the monitoring plugin.
Concerning the bridge with gmail accounts, can you help me in private to set up 
that?
Currently, I'm only using users on my openfire server without external links.

Original comment by Florent....@gmail.com on 22 Feb 2014 at 2:34

[GoogleCodeExporter]

Just have a gtalksms phone talk to Openfire, and connect to the 
gtalksms/openfire JID from a gmail account? It means you'll have to make a 
public server for the s2s to work. I'm not sure how much I can help with that, 
since I really don't have much time to troubleshoot your issue. Maybe someone 
else with a public jabber server can help - I don't think it's 
Openfire-specific.

Original comment by mcwerew...@gmail.com on 22 Feb 2014 at 5:12

[GoogleCodeExporter]

Ok, FYI, some modifications on the message delivery have been done between 
4.4.1 and 4.4.4. So the issue might already be fixed.
Can you keep me posted if you have the same issue with newer versions?

Original comment by Florent....@gmail.com on 23 Feb 2014 at 3:08

[GoogleCodeExporter]

Sure thing. I'll keep an eye on it, and if I see more of these issues with the 
later version I'll amend this bug.

Original comment by mcwerew...@gmail.com on 23 Feb 2014 at 6:39

[GoogleCodeExporter]

Closing.
Please reopen if the issue still occurs

Original comment by Florent....@gmail.com on 7 Mar 2015 at 12:12

[GoogleCodeExporter]

Original comment by Florent....@gmail.com on 7 Mar 2015 at 12:13

• Changed state: Deployed