btw, Is there any way to avoid the queue re-insertion? what if i just want 
messages to be sent just once, no matter if they are sent or failed? that's 
actually why i tried to set those 2 values to zero..

On Wednesday, September 5, 2012 11:03:17 AM UTC-3, Juan Bressan wrote:
>
> Awesome.. I didn't know the difference between those QUEUE & OUTBOUND 
> variables.. now that you posted this example I can see it clearly, as the 
> default values for both variables was 3, basically each wrong destination 
> was retried 9 times.. but at that time I didn't know how to enable smslib's 
> log, and when i finally did it i set both variables to 0.. and that caused 
> the "try forever" thing.
>
> Thank you very much man.
>
> On Wednesday, September 5, 2012 4:17:33 AM UTC-3, Thanasis wrote:
>>
>> Hi,
>>
>> Cannot reproduce this, seems to work fine with v3.5.2
>> Don't set these settings to zero (0) - it means "try for ever". These two 
>> settings (QUEUE & OUTBOUND) are multipled
>>
>> My test is this:
>>
>> Service.getInstance().S.QUEUE_RETRIES   = 2;
>> Service.getInstance().S.OUTBOUND_RETRIES= 1;
>>
>> 22776  2012-09-05 10:11:24,862 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.ModemGateway  - GTW: modem.com1: Sending Pdu: 
>> 079103962491000011000CD06432994C26030000FF12C8329BFD0699E5EF3668DA9C32D3E210
>> 22776  2012-09-05 10:11:24,862 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: SEND :AT+CMGS=30(cr)
>> 22976  2012-09-05 10:11:25,062 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: clearBuffer() called.
>> 23976  2012-09-05 10:11:26,062 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: SEND 
>> :079103962491000011000CD06432994C26030000FF12C8329BFD0699E5EF3668DA9C32D3E210
>> 26601  2012-09-05 10:11:28,687 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: BUFFER: +CMS ERROR: 38
>> 26602  2012-09-05 10:11:28,688 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: RECV :+CMS ERROR: 38(cr)
>> 26602  2012-09-05 10:11:28,688 [QueueManager [modem.com1]] ERROR 
>> org.smslib.modem.athandler.ATHandler  - GTW: modem.com1: CMS Error 38: Quit 
>> retrying, message lost...
>> 26602  2012-09-05 10:11:28,688 [QueueManager [modem.com1]] INFO  
>> org.smslib.AGateway$QueueManager  - GTW: modem.com1: Reinserting message to 
>> queue.
>>
>> ...
>> ...
>>
>> 33361  2012-09-05 10:11:35,447 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: SEND 
>> :079103962491000011000CD06432994C26030000FF12C8329BFD0699E5EF3668DA9C32D3E210
>> 36016  2012-09-05 10:11:38,102 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: BUFFER: +CMS ERROR: 38
>> 36016  2012-09-05 10:11:38,102 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: RECV :+CMS ERROR: 38(cr)
>> 36016  2012-09-05 10:11:38,102 [QueueManager [modem.com1]] ERROR 
>> org.smslib.modem.athandler.ATHandler  - GTW: modem.com1: CMS Error 38: Quit 
>> retrying, message lost...
>> 36017  2012-09-05 10:11:38,103 [QueueManager [modem.com1]] INFO  
>> org.smslib.AGateway$QueueManager  - GTW: modem.com1: Reinserting message to 
>> queue.
>>
>> ...
>> ...
>>
>> 41022  2012-09-05 10:11:43,108 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.ModemGateway  - GTW: modem.com1: Sending Pdu: 
>> 079103962491000011000CD06432994C26030000FF12C8329BFD0699E5EF3668DA9C32D3E210
>> 41022  2012-09-05 10:11:43,108 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: SEND :AT+CMGS=30(cr)
>> 41223  2012-09-05 10:11:43,309 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: clearBuffer() called.
>> 42223  2012-09-05 10:11:44,309 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: SEND 
>> :079103962491000011000CD06432994C26030000FF12C8329BFD0699E5EF3668DA9C32D3E210
>> 44905  2012-09-05 10:11:46,991 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: BUFFER: +CMS ERROR: 38
>> 44905  2012-09-05 10:11:46,991 [QueueManager [modem.com1]] DEBUG 
>> org.smslib.modem.AModemDriver  - GTW: modem.com1: RECV :+CMS ERROR: 38(cr)
>> 44905  2012-09-05 10:11:46,991 [QueueManager [modem.com1]] ERROR 
>> org.smslib.modem.athandler.ATHandler  - GTW: modem.com1: CMS Error 38: Quit 
>> retrying, message lost...
>> 44906  2012-09-05 10:11:46,992 [QueueManager [modem.com1]] WARN  
>> org.smslib.AGateway$QueueManager  - GTW: modem.com1: Maximum number of 
>> queue retries exceeded, message lost.
>>
>> I don't see any related issue which was fixed in v3.5.2.
>> Can you upgrade to the latest version? Check: 
>> https://smslib.googlecode.com/svn/smslib/tags/v3.5.2/RELEASE-NOTES.html
>>
>> On 5 September 2012 00:20, SMSLib Discussion Group on behalf of Juan 
>> Bressan <
>> smslib+noreply-apn2wqdzhcsxmtac3tmugsh6enraa7gwza0eofz4yk-yo-...@googlegroups.com
>> > wrote:
>>
>>> Hey, i'd been using sendMessage() before and everything was working ok. 
>>> Now switched to queueMessage(), and whenever the destination doesn't exist, 
>>> i get CMS ERROR 300, that's ok, but the thing is that smslib doesn't stop 
>>> retrying after 3 attempts as it's supposed to. It just keeps retrying all 
>>> the time. I'm using smslib 3.5.1.
>>>
>>> I've already tried setting these two variables but i don't see any 
>>> change:
>>>       Service.getInstance().S.QUEUE_RETRIES   = 0;
>>>       Service.getInstance().S.OUTBOUND_RETRIES= 0;
>>>
>>>
>>> Any hints?
>>>
>>> 157326 2012-09-04 17:22:09,747 [QueueManager [modem.com.moto]] DEBUG 
>>> org.smslib.modem.AModemDriver  - GTW: modem.com.moto: BUFFER: +CMS ERROR: 
>>> 300
>>> 157326 2012-09-04 17:22:09,747 [QueueManager [modem.com.moto]] DEBUG 
>>> org.smslib.modem.AModemDriver  - GTW: modem.com.moto: RECV :+CMS ERROR: 
>>> 300(cr)
>>> 157326 2012-09-04 17:22:09,747 [QueueManager [modem.com.moto]] WARN 
>>>  org.smslib.modem.athandler.ATHandler  - GTW: modem.com.moto: CMS Error 
>>> 300: Retrying...
>>>
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "SMSLib Discussion Group" group.
>>> To post to this group, send email to [email protected].
>>> To unsubscribe from this group, send email to 
>>> [email protected].
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msg/smslib/-/lzGlAV-lfgYJ.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"SMSLib Discussion Group" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msg/smslib/-/vP3M2QtbCSYJ.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to