'Channel' opened but not safely closed
Reports Channel
resources that are not safely closed, including any instances created by calling getChannel()
on a file or socket resource.
By default, the inspection assumes that the resources can be closed by any method with 'close' or 'cleanup' in its name.
Example:
void send(Socket socket) throws IOException {
SocketChannel channel = socket.getChannel(); //warning
channel.write(ByteBuffer.wrap("message".getBytes()));
}
- 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.
ChannelOpenedButNotSafelyClosed
Use the following options to configure the inspection:
Whether a
Channel
resource is allowed to be opened inside atry
block. This style is less desirable because it is more verbose than opening aChannel
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 'Channel' 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 |