'Channel' opened but not safely closed | Inspectopedia Documentation
 

'Channel' opened but not safely closed

Last modified: 03 December 2024

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:

Use the following options to configure the inspection:

  • Whether a Channel resource is allowed to be opened inside a try block. This style is less desirable because it is more verbose than opening a Channel in front of a try block.

  • Whether the resource can be closed by any method call with the resource passed as argument.