Customer is upgrading from EAP 7.4.14 to EAP 8.0.1

A Transaction (B) with propagation REQUIRES_NEW should be able to write to database, even though a surrounding transaction (A) has been marked for rollbackOnly.

They attached a reproducer for this issue and a sample xa datasource.

Process to reproduce:

Once successfully deployed, you just have to trigger the REST-Controller with a GET-Request on its endpoint URL.

For example: http://localhost:8080/tx-reproducer-1.0-SNAPSHOT/person/35

The PersonController should kick in and handle the request, delegating the call to the PersonService. This Class is calling the LoggingService twice. Therefore I’m expecting to see two records in the table REPRODUCER_LOGGING, because the method LoggingService#logToDatabsase is annotated with @Transactional(propagation = Propagation.REQUIRES_NEW). But when I look into the table REPRODUCER_LOGGING, I can only see one record.