That's fine. Its a deadlock of the notification thread, so don't worry too much :)
2009/11/3 Alex <[email protected]> > > Hi Thanasis, > > That is indeed the behaviour I see. I've made my threads into daemons > though, and they now shutdown fine. Hopefully this doesn't violate > any fundamental rules. > > Alex > > On Nov 2, 7:44 pm, Thanasis <[email protected]> wrote: > > I think (and hope!) that you are referring to this: > http://code.google.com/p/smslib/issues/detail?id=288 > > > > The end result is that during Service shutdown, the SMSLib does not > > terminate. Is this the behaviour you see? > > > > 2009/11/2 Alex <[email protected]> > > > > > > > > > > > > > Hi there, > > > > > I have an application using SMSLib. I am running on a Windows > > > machine. > > > > > My application attempts to connects to ports which may or may not have > > > a compatible device attached to them. I have noticed when my > > > application is shutting down, some threads handling serial connections > > > will block, e.g.: > > > > > Win32SerialPort.nwrite(byte[], int, int) line: not available [native > > > method] > > > Win32SerialPort.write(byte[], int, int) line: 672 > > > Win32SerialPort.write(int) line: 664 > > > Win32SerialOutputStream.write(int) line: 34 > > > ...etc. > > > > > There doesn't seem to be any clean way out of this, except for making > > > the thread which triggers this blocking call into a daemon thread. > > > Does this seem a reasonable solution? > > > > > Cheers, > > > > > Alex > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SMSLib for Java 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 -~----------~----~----~----~------~----~------~--~---
