Oops... The correct issue URL is: http://code.google.com/p/smslib/issues/detail?id=148
On Nov 12, 9:31 pm, Thanasis <[EMAIL PROTECTED]> wrote: > Hi, > > The current SMSLib is not 100% predictable in these situations. > This (sometimes) is due to the fact that these "violent" errors are not > propagated correctly via javacomm. > > I've added a RFE (http://code.google.com/p/smslib/issues/list?thanks=148) in > order to check these situations again. You may want to star it in order to > get notifications. > > 2008/11/12 Digiloo <[EMAIL PROTECTED]> > > > > > > > Hi > > > I start a new Service() and all went well until I intentionally (for > > testing purpose) > > remove the GSM Modem dongle: > > > 75204 [Win32SerialPort Notification thread] ERROR org.smslib - GTW: > > gsmmodem: Overrun Error! > > 75204 [Win32SerialPort Notification thread] ERROR org.smslib - GTW: > > gsmmodem: Parity Error! > > 75204 [Win32SerialPort Notification thread] ERROR org.smslib - GTW: > > gsmmodem: Framing Error! > > 75204 [Win32SerialPort Notification thread] ERROR org.smslib - GTW: > > gsmmodem: Overrun Error! > > 75204 [Win32SerialPort Notification thread] ERROR org.smslib - GTW: > > gsmmodem: Parity Error! > > > How do I catch this error? > > > / Hakan- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SMSLib Users 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 -~----------~----~----~----~------~----~------~--~---
