I think that you should all give v3.4.1 a try (or even better,
checkout the trunk repo directory). Even if its just a trial run. I
know that v3.4 has some design changes and this makes transition a bit
difficult, but I can't issue patches for older versions...

By the way, is this problem a self healing one? I mean, apart from the
delay in restarting the modems, does SMSLib resume ok after this
error?

On Jul 7, 4:47 pm, Jay <[email protected]> wrote:
> Hi Karthik and Thanasis
>
> Thanasis, sorry, I emailed you as well but I face a similar issue and
> I am also using 3.3.3 with a MultiTech Modem
>
> The exception I get is:
> 3624780 [SMSServer - OutboundPollingThread] INFO org.smslib  -
> SMSServer: sending asynchronously...
> 3624792 [SMSLib-QueueManager] WARN org.smslib  - GTW: modem1: Queue
> exception, marking gateway for reset.
> java.lang.StringIndexOutOfBoundsException: String index out of range:
> -1
>         at java.lang.StringBuffer.charAt(StringBuffer.java:163)
>         at org.smslib.modem.AModemDriver.getResponse(AModemDriver.java:
> 323)
>         at org.smslib.modem.athandler.ATHandler.sendMessage
> (ATHandler.java:337)
>         at org.smslib.modem.ModemGateway.sendMessagePDU
> (ModemGateway.java:402)
>         at org.smslib.modem.ModemGateway.sendMessage(ModemGateway.java:
> 206)
>         at org.smslib.AGateway$QueueManager.run(AGateway.java:711)
>         at java.lang.Thread.run(Thread.java:595)
> 3624792 [SMSLib-QueueManager] INFO org.smslib  - GTW: modem1:
> QueueManager stopped.
> 3628284 [SMSLib-WatchDog] INFO org.smslib  - WatchDog running...
> 3628284 [SMSLib-WatchDog] DEBUG org.smslib  - Draining messages:
> Gateway: modem1 restarting...
>
> It seems the server is expecting a response, and does not receive one,
> or it receives one and it is not properly formatted
>
> This happens around 50% of the time through normal use, and it
> generally seems to happen only if sending more than one message such
> as when sending 4 messages back to back, usually the 2nd, third or 4th
> messages causes this exception
>
> Any guidance you could provide would be greatly appreciated
>
> Sincerely,
>
> Jay
>
> On Jul 2, 8:57 pm, Karthik <[email protected]> wrote:
>
>
>
> > Thanks Thanasis,
> > ya, it occurs randomly, but it becomes a bigger problem for my
> > project. By upgrading the version will the solve this problem?...
>
> > On Jul 1, 3:01 pm, Thanasis <[email protected]> wrote:
>
> > > Hi,
>
> > > You are a bit behind in versions...
> > > Is this a random error?
>
> > > Try with the latest v3.3 release (v3.3.3) and see if this error
> > > persists.
> > > Alternatively, plan your upgrade to 3.4
>
> > > On Jul 1, 10:41 am, Karthik <[email protected]> wrote:
>
> > > > Hi Thanasis,
>
> > > > I got the following exception,
>
> > > > Exception in thread "SMSLib-AsyncMessageProcessor : test1"
> > > > java.lang.StringIndexOutOfBoundsException: String index out of range:
> > > > -1
> > > >         at java.lang.String.substring(Unknown Source)
> > > >         at 
> > > > org.smslib.modem.ModemGateway.readMessagesPDU(ModemGateway.java:
> > > > 400)
> > > >         at 
> > > > org.smslib.modem.ModemGateway.readMessages(ModemGateway.java:147)
> > > >         at org.smslib.modem.AModemDriver$AsyncMessageProcessor.run
> > > > (AModemDriver.java:895)
>
> > > > When this comes the smslib doesn't delete the messages after reading
> > > > those messages from the SIM.
>
> > > > I am using the SMSLib version 3.3.
>
> > > > Please give the solution for this thread.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SMSLib User Group" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/SMSLib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to