Inspectopedia 2026.3 Help

Incorrect @Transactional propagation on a @TransactionalEventListener method

Reports @TransactionalEventListener methods that are also annotated with a plain @Transactional.

A transactional event listener runs during the cleanup phase of the original transaction, which is still active but in an undefined state. A regular @Transactional therefore executes in an undefined transactional state and fails at runtime. The combination is valid only when the propagation is REQUIRES_NEW or NOT_SUPPORTED, or when the method is also annotated with @Async (which runs the listener on a separate thread with a clean transactional slate).

Example:

@Component class MyListener { @Transactional // reports: runs in an undefined transactional state @TransactionalEventListener void on(MyEvent event) { ... } }
@Component class MyListener { @Transactional(propagation = Propagation.REQUIRES_NEW) @TransactionalEventListener void on(MyEvent event) { ... } }

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.

SpringTransactionalEventListenerInspection
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 Core | Code

Inspection ID: SpringTransactionalEventListenerInspection

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 SpringTransactionalEventListenerInspection

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 2026.3, Qodana for JVM 2026.3,

Last modified: 20 November 2026