when does the methods socket.close() and someStream.close() throws IOException?
and how can I solve the problem?
thanks
benny.
when does the methods socket.close() and someStream.close() throws IOException? and how can I solve
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
when does the methods socket.close() and someStream.close() throws IOException?
and how can I solve the problem?
thanks
benny.
Not checking the return value of close() is a common but nevertheless serious programming error. It is quite possible that errors on a previous write(2) operation are first reported at the final close(). Not checking the return value when closing the file may lead to silent loss of data. This can especially be observed with NFS and with disk quota.
While closing a readonly stream can’t throw, java’s IO framework can’t check for that as it doesn’t have statically checked read vs. write streams