| Overall outbound message queue size |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2014 ⬆ |
◄ ► |
| Author | Message | |||
| Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 282 Registered: 07-2006 |
Hi Des, I know that is possible to limit queue on user basis but if you have many users that means multiplied queue size which can affect system stability. I think you should limit it somehow. Regards, Alex K. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4407 Registered: 08-2008 |
Hi Alex, I agree with you. I actually find it very odd that we would have a user based limit and not an overall system based limit. I will make sure to get this into our development queue. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4481 Registered: 08-2008 |
Follow-up... A setting was added in the update at http://www.nowsms.com/download/nowsms20130515.zip * SMS Gateway: Add configuration setting to limit flooding the outbound message queue. This setting enforces a maximum number of messages in outbound message queue. If a user attempts to submit additional messages when over the limit, a throttling error will be returned. To enable this throttling, the setting OutboundQueueLimit=##### must be added to the [SMSGW] section of SMSGW.INI. (Note that settings also exist to limit the number of outbound queued messages from specific user accounts. Refer to UserOutboundQueueLimit for user account based limits.) | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 144 Registered: 08-2006 |
Hi Des This was added in 2013-04-30 right? Regards Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4489 Registered: 08-2008 |
That's what changes.txt says ... I'm just trying to update posts that requested functionality that has recently been added.  | |||
| Alex Kaiser Frequent Contributor Username: Alex_k Post Number: 283 Registered: 07-2006 |
Hi Des, Thanks for the update. We'll put it in test this week. Regards, Alex K. | |||
| Mathew Mathachan New member Username: Mathewm Post Number: 44 Registered: 04-2011 |
Hi Des, The throttling error is returned as HTTP Status code 403 (Forbidden). 403 is also returned for other condition like wrong SMSRoute/Invalid URL etc... Is there a way to differentiate Throttling error from other errors? :- Mathew | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4742 Registered: 08-2008 |
Hi Mathew, I'm not sure exactly when we changed this, but we had a large customer complain that 403 Forbidden was not really accurate in the case of a throttling/quota issue. They convinced us that instead a 503 Service Unavailable status response was more appropriate. At some point during this past summer this was changed, as I confirmed the 2013.09.26 version is returning 503 as a throttling response for any quota related issues. I'm surprised that we did not make this configurable when we made that change, but the HTTP status code is hard coded. -- Des NowSMS Support | |||
| Mathew Mathachan New member Username: Mathewm Post Number: 45 Registered: 04-2011 |
Thanks Des | |||
