https://github.com/cepr0/sb-reactive-transaction-publishing-event-issue
Issue with the behavior of the 'event listener' methods when events are published within the transactional reactive methods in Spring Boot 2.2.0.M3
https://github.com/cepr0/sb-reactive-transaction-publishing-event-issue
reactive spring spring-boot transactions
Last synced: about 2 months ago
JSON representation
Issue with the behavior of the 'event listener' methods when events are published within the transactional reactive methods in Spring Boot 2.2.0.M3
- Host: GitHub
- URL: https://github.com/cepr0/sb-reactive-transaction-publishing-event-issue
- Owner: Cepr0
- Created: 2019-06-10T20:42:07.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2019-07-12T10:28:34.000Z (almost 7 years ago)
- Last Synced: 2025-01-17T22:09:10.962Z (over 1 year ago)
- Topics: reactive, spring, spring-boot, transactions
- Language: Java
- Homepage:
- Size: 19.5 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
This demo demonstrates the issue with the behavior of the 'event listener' methods
when events are published within the transactional reactive methods
in Spring Boot 2.2.0.M3.
**Sample reactive method**
```java
@Transactional
public Mono create(Model model, ModelEvent.Type type) {
return repo.save(model)
.doOnSuccess(m -> publisher.publishEvent(new ModelEvent(m, type)));
}
```
**Normal behavior**
The following code works as expected. The method is invoked within the current transaction -
if we uncomment the throwing the exception then the current transaction will be rolled back.
```java
@EventListener(condition = "#event.normal()")
public void handleNormalEvent(ModelEvent event) {
log.info("[i] Handled event: {}", event.getModel());
// throw new RuntimeException("Oops, something went wrong...");
}
```
**IllegalStateException is raised**
If we add `@Transactional` annotation with `MANDATORY` propagation parameter to check that
the 'event listener' method is invoked in the existent transaction,
then the `IllegalStateException` is raised with a message:
`Specified transaction manager is not a PlatformTransactionManager:
org.springframework.data.mongodb.ReactiveMongoTransactionManager`
```java
@Transactional(propagation = Propagation.MANDATORY)
@EventListener(condition = withTransactional)
public void handleEventWithTransactional(ModelEvent event) {
log.info("[i] Handled event: {}, with transactional", event.getModel());
}
```
**@TransactionalEventListener**
If we use `@TransactionalEventListener` (instead of `@EventListener`) then
the 'event listener' method is not invoked at all.
```java
// @Async
@TransactionalEventListener(condition = "#event.inTransactionEventListener()")
public void handleEventInTransactionEventListener(ModelEvent event) {
log.info("[i] Handled event: {}, in transactional event listener", event.getModel());
}
```
**Reproducing the issue**
1) Start a MongoDB Replica Set cluster (within the project folder)
```bash
docker-compose up -d
```
2) Start the application
```bash
mvn spring-boot:run
```
(or you can start cluster simply with the application: `mvn spring-boot:run -Dspring.profiles.active=replSet`)
3) Run the requests from the `demo-requests.http` file
(or you can run the application and requests within Intellij IDEA)
4) Don't forget to stop the cluster if you explicitly start it
```bash
docker-compose down
```
Or you can check the [`ModelHandlerTest`](src/test/java/io/github/cepr0/issue/ModelHandlerTest.java) class.
**Requirements**
Docker, Docker Compose, Java 8, Maven