Connection opened but not safely closed

Reports Java ME javax.microedition.io.Connection resources that are not opened in front of a try block and closed in the corresponding finally block. Such resources may be inadvertently leaked if an exception is thrown before the resource is closed.

Example:

  void example() throws IOException {
    Connection c = Connector.open("foo");
  }

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.

ConnectionOpenedButNotSafelyClosed

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.

Inspection ID: ConnectionResource

Inspection options

Here you can find the description of settings available for the Connection opened but not safely closed inspection, and the reference of their default values.

Allow resource to be opened inside a 'try' block

Option ID:

insideTryAllowed

Default value:

Not selected

Any method may close resource argument

Option ID:

anyMethodMayClose

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:

//noinspection ConnectionOpenedButNotSafelyClosed

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

IntelliJ IDEA 2025.3

Inspection Details
By default bundled with:	IntelliJ IDEA 2025.3, Qodana for JVM 2025.3,

Last modified: 03 December 2025