| Duplicated messages - Memory leak |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Martín Mendiguren New member Username: Martin_ Post Number: 2 Registered: 04-2006 |
Hello Brice. Last week I sent an e-mail with two problems that we had using the WTLS 2.57 and the NowSMS v.5.51k The first problem was that the sender sometime were changed in the logs and that problem was resolved when we upgraded WTLS to version 2.58. We still have de second problem. Some MMS are sent two ore more times. The MMSs are logged OK in the MMSC.log so we put a debug between the GGSN and the WTLS and we found that sometimes the MMSC didn’t send the “MMS M-Send-Confirmation”. I attached the ethereal debug archive (pcap_error ) where you can find the error. In the line 201 you can find the “MMS m-sent-request” but then the “MMS M-Send-Confirmation” is not sent but the MMS reached the mobile destiny. The mobile sent the “MMS m-sent-request” for a second time (line 225) and the “MMS M-Send-Confirmation” is sent by the MMS. The MMS arrive at the mobile destiny 2 times and the log shows 2 MMSs sent with its 2 retrieves. This is an error, because we will charge the client for two MMS but he sent only one. Although with the upgrade we solve the first problem, now we have one problem that we didn’t have before: the memory used by the NowSMS begin to increase until it reached the full capacity of the PC. I attached a file with the memory log of NowSMS. When the memory reach 100 % the MMSC doesn’t send MMS any more until we reset the service. Do you believe this problem will be resolved if we upgrade to NowSMS v2006? Do you think that we need to upgrade the HW? Thanks Martín
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5951 Registered: 10-2002 |
Hi Martín, I am concerned about the apparent memory leak. There are 3 possibilities, but it it hard to think of the quickest way to diagnose. Let me explain what I think the possibilities are: 1.) The system (hardware) is overloaded, causing requests to backlog, and the queued requests take more and more memory, and the system does not have enough resources to recover. 2.) There is a corrupt message file somewhere on the system, and the system is struggling to process it. (We occasionally had these problems years ago, and all known problems have been fixed.) 3.) Some other software bug is causing a problem. My suspicion is #1. But this can be hard to diagnose for certain. Is it possible for me to connect remotely to your system using VNC or Remote Desktop? (If you are with the customer that I am thinking of, I have connected to their system remotely using VNC to diagnose problems in the past.) If a connection with VNC is possible, then send me an e-mail at nowsms@now.co.uk, with "Attention: Bryce" in the subject line, and I will give you my current IP address details. If VNC or Remote Desktop is not possible, then I will have to think more about what we can do to diagnose the problem. There are some very significant performance improvements in NowSMS 2006 when there are a large number of users defined to the MMSC. That could also be an issue that you are encountering. I could diagnose that pretty quickly if it is possible to connect in remotely. -bn | ||||
| Martín Mendiguren New member Username: Martin_ Post Number: 4 Registered: 04-2006 |
Hello Brice. You can connect remotly using VNC. We will contact you by e-mail for the details. Thanks Martin | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5954 Registered: 10-2002 |
Martin, I haven't gotten your e-mail yet. But I'm wondering, did you recently update to v5.51k? If so, then I think that might be the problem. You have a very large number of users on your MMSC. When I connected with VNC late last year, I put a special version of MMSC.EXE and MMSCDLL.DLL on the system. It contained performance optimisations for systems with very large numbers of MMSC users. This special version contained some features that were going to be standard in the NowSMS 2006. I'll be looking for your e-mail. But in the meantime, also check MMSC.EXE, and see if the date/time stamp is from November 1, 2005. -bn | ||||
files
