Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Closing a SerialPort causes an IOException to be thrown #3

Closed
rm5248 opened this issue Feb 13, 2016 · 1 comment
Closed

Closing a SerialPort causes an IOException to be thrown #3

rm5248 opened this issue Feb 13, 2016 · 1 comment

Comments

@rm5248
Copy link
Owner

rm5248 commented Feb 13, 2016

When closing a SerialPort, the thread that is currently reading the port will come back with an IOException. This occurs at least on Windows using a BufferedSerialInputStream, but not using a SimpleSerialInputStream.

Also, when closing a serialport that is using a SimpleSerialInputStream, a 0 gets returned when the serial port closes - it should be -1, as that is what an InputStream uses to say that there is an EOF.
@rm5248 rm5248 mentioned this issue Feb 14, 2016
Closed
rm5248 added a commit that referenced this issue Feb 15, 2016
@rm5248
fixing bugs #2 and #3
b1a445e 
Updated BufferedSerialInputStream to optionally throw an IOException
when an InterruptedException is thrown.  Added a function on the
SerialPort to set this functionality.  Fixed the inputstream returning 0
when the serial port is closed(at least on Windows), will now return -1.
Needs to be tested on Linux.  POM should no longer try to sign by
default, only when we release.
rm5248 added a commit that referenced this issue Feb 22, 2016
@rm5248
Fixing native code for bug #3. Added logger to native code. updated n…
30c0c85 
…ative code to return -1 on EOF on *nix systems. still needs some testing, but it should be good.
@rm5248
Copy link
Owner Author

rm5248 commented Mar 5, 2016

Should be fixed with 0.7.

@rm5248 rm5248 closed this as completed Mar 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rm5248