| NowSMS degraded performance |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 03, 2020 ⬆ |
◄ ► |
| Author | Message | |||
| Jordan New member Username: Jordan9284 Post Number: 8 Registered: 07-2019 |
Hi Support, We have noticed recently when making any changes to our NowSMS application we see an immediate decrease in NowSMS performance and have a queue build. This is when adding new SMSC connections or SMS users To resolve the issue we find that we have to restart the NowSMS gateway service. Do we have to restart the Gateway service after making any changes | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 6068 Registered: 08-2008 |
Hi Jordan, That is very unusual...not something that I can recall seeing before. Is there a large number of SMSC connections? There is a possibility that adding a connection may cause some existing connections to disconnect and then reconnect...but this is not a time consuming process. I’d be very surprised if it took more than a minute or two. Does the SMSOUT-yyyymmdd.LOG reference any connection errors during this time period? Adding SMS users should have absolutely no effect, so I am more confused about how this could have any effect on performance. One idea...there is a “priority” attribute that can be assigned to user accounts. We have been investigating an odd issue where a logic error could cause a priority message to get stuck and cause a queue buildup. The problem that we observed had a different cause, but there is a chance it may be related to the problem you are experiencing. If you have any user accounts flagged as “priority”, it may be a good idea to remove this setting from all accounts, We do have an interim update that addresses the priority queue processing problem (latest version https://www.nowsms.com/download/nowsms20191024.zip). But as I can’t guarantee this will fix the problem you are seeing, it’s a better idea to remove this priority attribute from any accounts as a first step in troubleshooting. The next step, if the problem does not occur, would be to try to recreate the problem with the SMSDEBUG.LOG enabled. — Des NowSMS Support | |||
