Support forum
Add Reply
Add Topic9:21 pm
May 28, 2013
Offline
QuotePlease send the serial number of your license and your feature request to email address dms@diafaan.com and I will add it to the list of requested features. If it is not too complicated to implement we can add it to the next version of Diafaan SMS Server and I can send you a plugin to test it out in the current version.
Regards, Henk
2:30 pm
Hi thanks for the reply and understood:
so basically the maxmessagesperminute is somehow max messages per 2 minutes..understood that Diafaan also counts the rejected messages, witch in theory, they should be a byproduct of the maxmessagesperminute limitation...
any feature upgrade planned so we can limit the accepted # of messages per minute ex 20 ? the idea is to throttle the client during peak times to a specific number of accepted messages in 1 minute , while rejecting the overflow attempts..
Thanks
12:05 pm
May 28, 2013
Offline
Hello player1,
The SMPP Connector responds with a throttling error if the sum of the messages of two whole consecutive minutes exceeds two times the MaxMessagesPerMinute value. Each submitted message is counted, also the messages that trigger the throttling error.
For example, if MaxMessagesPerMinute is set to 30 and the SMPP client sends 60 messages in minute 8:30, all 60 messages will be accepted. However, all messages that are sent in minute 8:31 will be rejected. The rejected messages in minute 8:31 will also be counted for the throttling in minute 8:32.
The throttling error is a warning that the SMPP client sends too many message. When MaxMessagesPerMinute is set in the SMPP Connector then the SMPP client should not send more than the allowed amount of messages per minute.
Regards, Henk
10:20 am
HI, we have the following issues with MaxMEssagesPerMinute on the connector side :
With MaxMessagesPerMinute=30, Diafaan accepts only one submit_sm per clock minute and rejects all subsequent attempts (~59) with ESME_RTHROTTLED. Same behaviour observed at MaxMessagesPerMinute=20. At MaxMessagesPerMinute=60 the limiter works correctly (proportional throughput). Reproduced over a 24-minute sustained-load window.
Configuration at time of capture: MaxMessagesPerMinute=30, applied via HTTP API set-connector-property with reload=1. Property confirmed via request-server-status after the change.
ESME load: ~60 submit_sm/minute steady (single bind, sustained).
Log evidence — 12 consecutive submit_sm_resp error:Throttling error lines spanning 11 seconds, with no accepted responses interleaved. Sequence numbers monotonically increasing (377206357 → 377207620), confirming each is a distinct submit. This was approximately 2 minutes after applying MaxMessagesPerMinute=30 (well past any reload-settling window):
2026/05/18 19:54:01.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377206357 message_id:
2026/05/18 19:54:02.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377206423 message_id:
2026/05/18 19:54:03.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377206425 message_id:
2026/05/18 19:54:04.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377206427 message_id:
2026/05/18 19:54:05.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377206429 message_id:
2026/05/18 19:54:06.530 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377207376 message_id:
2026/05/18 19:54:07.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377207378 message_id:
2026/05/18 19:54:08.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377207380 message_id:
2026/05/18 19:54:09.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377207383 message_id:
2026/05/18 19:54:10.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377207614 message_id:
2026/05/18 19:54:11.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377207618 message_id:
2026/05/18 19:54:12.515 58839 - command:submit_sm_resp error:Throttling error (ESME has exceeded allowed message limits) sequence:377207620 message_id:
The actual longest continuous-reject run inside this single minute was 59 rejections in 59 seconds, with exactly 1 acceptance at the start of the minute.
Expected behaviour:
With MaxMessagesPerMinute=30, the first 30 submit_sms within a clock minute should be accepted, the next ~30 should be rejected. Total ~30 accepts / ~30 rejects per minute.
Observed behaviour:
1 accept / ~59 rejects per minute. Same at MaxMessagesPerMinute=20. Correct behaviour observed at MaxMessagesPerMinute=60.
Reproduction:
Configure connector MaxMessagesPerMinute=30
Bind ESME and send submit_sm at sustained 60/min
Observe connector log: only the first submit_sm of each clock minute receives submit_sm_resp status:ok; remainder receive submit_sm_resp error:Throttling error
Change to MaxMessagesPerMinute=60 and rerun — behaviour normalises
1 Guest(s)