Socket opened but not safely closed
Reports socket resources that are not safely closed. Socket resources reported by this inspection include java.net.Socket
, java.net.DatagramSocket
, and java.net.ServerSocket
.
By default, the inspection assumes that the resources can be closed by any method with 'close' or 'cleanup' in its name.
Example:
byte[] getMessage(ServerSocket socket) throws IOException {
Socket client = socket.accept(); //socket is not closed
return client.getInputStream().readAllBytes();
}
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
SocketOpenedButNotSafelyClosed
Use the following options to configure the inspection:
Whether a socket is allowed to be opened inside a
try
block. This style is less desirable because it is more verbose than opening a resource in front of atry
block.Whether the resource can be closed by any method call with the resource passed as argument.
Here you can find the description of settings available for the Socket opened but not safely closed inspection, and the reference of their default values.
Inspection Details | |
---|---|
By default bundled with: | |
Can be installed with plugin: | Java, 243.23126 |
Thanks for your feedback!