'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:
Locating this inspection
- 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- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
Use the following options to configure the inspection:
Whether a
Channelresource is allowed to be opened inside atryblock. This style is less desirable because it is more verbose than opening aChannelin front of atryblock.Whether the resource can be closed by any method call with the resource passed as argument.
Inspection options
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.
- Allow resource to be opened inside a 'try' block
Default value:
Not selected- Any method may close resource argument
Default value:
Selected
Suppressing Inspection
You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:
More detailed instructions as well as other ways and options that you have can be found in the product documentation:
Inspection Details | |
|---|---|
By default bundled with: |