TransactionRequiredException thrown although TransactionalAdvice annotated

[Wheedman]

Expected Behavior

The deletion in the database should work as expected.

Actual Behaviour

A TransactionalRequiredException is thrown

Steps To Reproduce

1. Use testcontainers with postgresql 11.8
2. Write a Micronaut-Test testing the following method

    @Override
    public int deleteAllSlugsLikeAndOlderThan(String query, Instant date) {
        String qlString = "DELETE FROM ArdmResultEntity AS s WHERE s.slug LIKE CONCAT('%', ?1, '%') AND s.createdAt < ?2";
        Query query = entityManager.createQuery(qlString)
            .setParameter(1, query.trim())
            .setParameter(2, date);

        int deletedRows = 0;

        try {
            deletedRows = query.executeUpdate();
        } catch (Exception e) {
           log.error("Deletion was not successful", e);
        }
        return deletedRows;
    }

4. TransactionRequiredException is thrown

Environment Information

No response

Example Application

No response

Version

3.5.2

[ojebari-ma]

Can you please confirm that this is still an issue in the latest version of Micronaut?

[graemerocher]

Triage: transferred from micronaut-core because this report concerns JPA/Hibernate transaction integration rather than the Core container. The report includes an update query and a TransactionRequiredException, but no example application or current environment details. Please confirm the latest Micronaut Data/SQL, Hibernate, JPA, database, and JDK versions and attach a minimal runnable reproducer. Likely checks are that TransactionalAdvice is applied to the concrete bean method (not self-invocation/final code), that the JPA transaction manager/session integration is present, and that the EntityManager used by the query is bound to the active transaction.