ERROR MESSAGE - Message Queue Full

ERROR MESSAGE - Message Queue Full SearchSearch
Author Message
iwan
Posted on Friday, October 03, 2003 - 06:42 pm:   

I have problem with NOW SMS Beta 5.0 , we encountered this error message :
F7E0CAD.req,127.0.0.1,+628561869573,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.46.14:30002
2003-10-03 23:24:04,3F7E0CAD.req,127.0.0.1,+628561869573,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.46.14:30002
2003-10-03 23:24:20,3F7E0CAD.req,127.0.0.1,+628561869573,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.46.14:30002
2003-10-03 23:24:36,3F7E0CAD.req,127.0.0.1,+628561869573,Retry Pending - ERROR: Message Queue Ful

This message blocked all the message to go through , and we already check with operator that the number +628561869573 turn off the phone and all the sms we sent is buffering at SMSC , the limit of the buffering is 100 SMS and when the 101 sms sent to this number the error message appear , please tell me how to avoid this thing to happened again and can i remove manually the "sending mechanism" which continue keep sending the message while the Message Queue full ?
I try to remove the file from "Q" directory and failed , the NOWSMS keep sending the message.
Bryce Norwood - NowSMS Support
Posted on Saturday, October 04, 2003 - 03:10 pm:   

Iwan,

That is interesting. I guess different SMSCs use this error code a little differently. A few months back, we encountered this error when a queue at an SMSC was having a problem. The SMSC itself was not accepting any messages during certain peak periods of the day, and would occasionally return this error.

We adjusted our implmentation to better cope with that situation.

In the situation you describe, I believe we should handle things a little differently, with longer delays between retries.

But a message like this shouldn't block other messages from being transmitted. At least I can't see how that could happen (unless the SMSC broke the link to us when the error occurred).

I'll run some tests, as perhaps the logic is not functioning as intended when this error occurs, which would indeed be a major problem. (So much for a relaxing weekend here. )

Can you confirm there were definitely other messages in that Q directory that were not being processed?

As for removing the file manually, you should be able to do this. The only problem that you might run into is a timing error. You might have to try the delete several times, as NowSMS would have the file locked open while it is trying to process the message, but there would be at least 15 second delays between processing attempts.

-bn
iwan
Posted on Sunday, October 05, 2003 - 03:12 am:   

Hi Mr Bryce

I am sorry about distrubing your week end :-( , i conformed that the message is blocked is more then 2 destination number are in having the same problem , i sent you some example on the log record :
req,127.0.0.1,+628562251453,OK -- SMPP - 202.155.4,Text=""
2003-10-05 00:00:32,3F7FA55F.req,127.0.0.1,+628562107656,OK -- SMPP - 202.155.,Text=" "
2003-10-05 00:00:32,3F7FA561.req,127.0.0.1,+628551025527,OK -- SMPP - 202.155.,Text=" "
2003-10-05 00:00:33,3F7F9B73.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.
2003-10-05 00:00:48,3F7F9C72.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.
2003-10-05 00:01:03,3F7FA044.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.
2003-10-05 00:01:18,3F7FA06A.req,127.0.0.1,+628557800420,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.
2003-10-05 00:01:33,3F7FA143.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.
2003-10-05 00:01:48,3F7FA1D6.req,127.0.0.1,+628557800420,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155.
2003-10-05 00:02:04,3F7F9B73.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.15
2003-10-05 00:02:19,3F7F9C72.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.1
2003-10-05 00:02:34,3F7FA044.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.1h
2003-10-05 00:02:49,3F7FA06A.req,127.0.0.1,+628557800420,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.
2003-10-05 00:03:04,3F7FA143.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 2
2003-10-05 00:03:19,3F7FA1D6.req,127.0.0.1,+628557800420,Retry Pending - ERROR: Message Queue Full -- SMPP -
2003-10-05 00:03:34,3F7FA562.req,127.0.0.1,+628568559401,OK -- SMPP - 202.155,Text=""
2003-10-05 00:03:34,3F7FA564.req,127.0.0.1,+628551025527,OK -- SMPP - 202.155.,Text=""
2003-10-05 00:03:35,3F7F9B73.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155
2003-10-05 00:03:50,3F7F9C72.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.
2003-10-05 00:04:05,3F7FA044.req,127.0.0.1,+628563332613,Retry Pending - ERROR: Message Queue Full -- SMPP - 202.155So all of the message can not sent if this Error occure at the 2 or more number, they keep trying to sent and the next sms for this 2 number already Queue in the next row to sent , this keep happening and cause all message behind this "marry go around" circle can not sent .
I discuss with SMSC operator, we can have some option to only retry 1,2,3 -or some number - times after the message cannot sent and they guess that the parameter compiled so i cannot set it manually.
Please help us Mr Bryce the services now operate manually to take alook if there are some Error block the sending, We did remove manually from Q directory for those message right now.

Best Regards
Iwan
Bryce Norwood - NowSMS Support
Posted on Tuesday, October 07, 2003 - 04:11 pm:   

Hi Iwan,

Sorry for the delay in follow-up.

We did some investigation and testing over the weekend.

I don't think that one (or more) of these messages would prevent other messages from being sent. However, they would produce a considerable slow down in outbound sending.

Every time this particular SMPP error condition is encountered, we would delay 15 seconds before retrying to send any more messages. (This is because we make the assumption that the entire receive queue is full on the SMSC ... not the queue for a particular phone number.)

But any other pending messages should definitely have been sent out, and it looks like they were based upon the excerpt from your log file above.

Based on this experience, we made some last minute changes on the v5.0 release, particularly focused on the SMPP environment.

When any errors occur, we wait a longer period of time before retrying the message on which an error occurred. Other messages will continue to be routed over the connection without any delay.

On this particular SMPP error, where the receive queue is full, we wait longer before we finally give up on the message (as opposed to other errors). Hopefully the retry timeouts will be made configurable in a future version ... in this version they are not.

-bn