Access to 'static' field locked on instance data

Reports access to non-constant static fields that are locked on either this or an instance field of this.

Locking a static field on instance data does not prevent the field from being modified by other instances, and thus may result in unexpected race conditions.

Example:

  static String test;
  public void foo() {
      synchronized (this) {
          System.out.println(test); // warning
      }
  }

There is a quick-fix that allows ignoring static fields of specific types. You can manage those ignored types in the inspection options.

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.

AccessToStaticFieldLockedOnInstance

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.

Settings or Preferences | Editor | Inspections | Java | Threading issues

Use the inspection options to specify which classes used for static fields should be ignored.

Inspection options

Here you can find the description of settings available for the Access to 'static' field locked on instance data inspection, and the reference of their default values.

Ignored classes: Empty

Availability

By default bundled with: IntelliJ IDEA 2024.1, Qodana for JVM 2024.1,
Can be installed with plugin: Java, 241.18072

Last modified: 18 June 2024