Inspectopedia 2025.2 Help

Suspicious Hooks.onOperatorDebug() usage

Reports the usage of Hooks.onOperatorDebug() when ReactorDebugAgent.init() is called.

If ReactorDebugAgent is in the classpath, and spring.reactor.debug-agent.enabled is true (default value), ReactorDebugAgent.init() is called automatically at startup. Using both Hooks.onOperatorDebug() and ReactorDebugAgent.init() cause doubled debugging stack frames generated by Reactor. Also, Hooks.onOperatorDebug() can cause performance overhead.

The quick-fix removes the invocation of Hooks.onOperatorDebug().

Example:

public void hook() { Hooks.onOperatorDebug(); // Reports 'Call Hooks.onOperatorDebug() while ReactorDebugAgent is initialized' }

After the quick-fix is applied:

public void hook() { }

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.

SpringBootReactorHooksOnDebug
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 | Spring | Spring Boot

This inspection only triggers when Spring Boot version for the project or module is 2.2.0 or higher.

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 SpringBootReactorHooksOnDebug

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:

IntelliJ IDEA 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025