Home/ Questions/Q 7186307
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T18:36:14+00:00

Good afternoon all. I am aware that if we close() an java.io.OutputStream , it

  • 0

Good afternoon all. I am aware that if we close() an java.io.OutputStream, it may throw an IOException when there are hard disk errors.

As for java.io.InputStream, Javamex states that:

A normal closure of a network socket actually involves a closure request (TCP/IP FIN packet) being sent over the connection and waiting for the other end to acknowledge this closure request. (In fact, the other end of the connection then in turn sends a closure request, which the closing end acknowledges.) So in the case of a socket input stream, a closure operation actually involves sending traffic over the connection and the closure can thus fail with an error.

Now I was wondering exactly under what circumstances will a java.io.InputStream (or sub class) for a local file (network access not needed) ever throw an exception when we call close() ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here’s one situation:

    • Another part of the application has mistakenly closed the underlying file descriptor associated with the InputStream. When the Java runtime calls the system close() function, it may get an EBADF error indicating that the file handle is invalid.

    The above situation probably indicates a serious bug somewhere else in the application.

    • 0